v.25.10Improvement
Setting enable_http_compression is now the default
The settingenable_http_compressionis now the default. This means that if a client accepts HTTP compression, the server will use it. However, this change has certain downsides. The client can request a heavy compression method, such asbzip2, which is unreasonable, and it will increase the resource consumption of the server (but this will be visible only when large results are transferred). The client can requestgzip, which is not that bad, but suboptimal compared tozstd. Closes #71591. #87703 (Alexey Milovidov).
Why it matters
This feature aims to improve network efficiency and reduce data transfer sizes by enabling HTTP compression by default. It solves the problem of uncompressed large result transfers, thereby saving bandwidth and potentially improving query response times. However, clients can request different compression methods, including heavy ones likebzip2, which may increase server resource usage.How to use it
To use this feature, no action is needed sinceenable_http_compression is enabled by default. Clients should include the appropriate Accept-Encoding HTTP header to specify their supported compression methods. The server will honor this and compress responses accordingly.