diff options
| author | Michael Paquier <michael@paquier.xyz> | 2022-01-07 13:48:59 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2022-01-07 13:48:59 +0900 |
| commit | 000f3adfdc4336df83777eba86ce48f36cb6c6e9 (patch) | |
| tree | 4963330f911b0668d7965bff939c4fbc40e47033 /src/backend/access/gist/gistxlog.c | |
| parent | 7ead9925ff94cfc9c3237672b7d19d5cc1b27ef5 (diff) | |
| download | postgresql-000f3adfdc4336df83777eba86ce48f36cb6c6e9.tar.gz postgresql-000f3adfdc4336df83777eba86ce48f36cb6c6e9.zip | |
Refactor tar method of walmethods.c to rely on the compression method
Since d62bcc8, the directory method of walmethods.c uses the compression
method to determine which code path to take. The tar method, used by
pg_basebackup --format=t, was inconsistent regarding that, as it relied
on the compression level to check if no compression or gzip should be
used. This commit makes the code more consistent as a whole in this
file, making the tar logic use a compression method rather than
assigning COMPRESSION_NONE that would be ignored.
The options of pg_basebackup are planned to be reworked but we are not
sure yet of the shape they should have as this has some dependency with
the integration of the server-side compression for base backups, so this
is left out for the moment. This change has as benefit to make easier
the future integration of new compression methods for the tar method of
walmethods.c, for the client-side compression.
Reviewed-by: Georgios Kokolatos
Discussion: https://postgr.es/m/Yb3GEgWwcu4wZDuA@paquier.xyz
Diffstat (limited to 'src/backend/access/gist/gistxlog.c')
0 files changed, 0 insertions, 0 deletions