Re: refactoring basebackup.c

On 7/8/21 9:26 PM, Robert Haas wrote:
> Here at last is a new version.
Please refer this scenario ,where backup target using
--server-compression is closing the server
unexpectedly if we don't provide -no-manifest option

[tushar(at)localhost bin]$ ./pg_basebackup --server-compression=gzip4  -t
server:/tmp/data_1  -Xnone
NOTICE:  WAL archiving is not enabled; you must ensure that all required
WAL segments are copied through other means to complete the backup
pg_basebackup: error: could not read COPY data: server closed the
connection unexpectedly
    This probably means the server terminated abnormally
    before or while processing the request.

if we try to check with -Ft then this same scenario  is working ?

[tushar(at)localhost bin]$ ./pg_basebackup --server-compression=gzip4  -Ft
-D data_0 -Xnone
NOTICE:  WAL archiving is not enabled; you must ensure that all required
WAL segments are copied through other means to complete the backup
[tushar(at)localhost bin]$

--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company