You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Replace BASE_BACKUP COMPRESSION_LEVEL option with COMPRESSION_DETAIL.
There are more compression parameters that can be specified than justan integer compression level, so rename the new COMPRESSION_LEVELoption to COMPRESSION_DETAIL before it gets released. Introduce aflexible syntax for that option to allow arbitrary options to bespecified without needing to adjust the main replication grammar,and common code to parse it that is shared between the client andthe server.This commit doesn't actually add any new compression parameters,so the only user-visible change is that you can now type somethinglike pg_basebackup --compress gzip:level=5 instead of writing justpg_basebackup --compress gzip:5. However, it should make it easy toadd new options. If for example gzip starts offering fries, we cansupport pg_basebackup --compress gzip:level=5,fries=true for thebenefit of users who want fries with that.Along the way, this fixes a few things in pg_basebackup so that thepg_basebackup can be used with a server-side compression algorithmthat pg_basebackup itself does not understand. For example,pg_basebackup --compress server-lz4 could still succeed even ifonly the server and not the client has LZ4 support, provided thatthe other options to pg_basebackup don't require the client todecompress the archive.Patch by me. Reviewed by Justin Pryzby and Dagfinn Ilmari Mannsåker.Discussion:http://postgr.es/m/CA+TgmoYvpetyRAbbg1M8b3-iHsaN4nsgmWPjOENu5-doHuJ7fA@mail.gmail.com