From: | Support <admin(at)e-blokos(dot)com> |
---|---|
To: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_basebackup cannot compress to STDOUNT |
Date: | 2020-05-08 19:31:45 |
Message-ID: | 70a49d18-c6cb-69e3-1ea8-ef09ebb5b579@e-blokos.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/8/2020 12:18 PM, Adrian Klaver wrote:
> On 5/8/20 12:14 PM, Support wrote:
>> Hi,
>>
>> Despite of the --help saying that it's possible to gzip to STDOUT and
>> pipe it for another process
>> pg_basebackup fails saying that it's not possible to gzip to STDOUT.
>
> 1) Postgres version?
>
> 2) Command run?
>
> 3) Error reported?
>
>>
>> Who to believe then?
>>
>>
1) Postgres version?
12.2 selt compiled with
./configure --with-perl --enable-integer-datetimes --enable-depend
--with-pam --with-systemd --enable-nls --with-libxslt --with-libxml
--with-llvm --with-python --with-icu --with-gssapi --with-openssl
2) Command run?
ssh postgres(at)nodeXXX "pg_basebackup -h /run/postgresql -Ft -D- | pigz -c
-p2 " | pigz -cd -p2 | tar -xf- -C /usr/local/pgsql/data
3) Error reported?
pg_basebackup: error: cannot stream write-ahead logs in tar mode to stdout
Try "pg_basebackup --help" for more information.
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
Thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2020-05-08 19:34:10 | Re: Odd postgres12 upgrade is changing or munging a password? |
Previous Message | Adrian Klaver | 2020-05-08 19:23:21 | Re: Odd postgres12 upgrade is changing or munging a password? |