From: | Maksim Milyutin <milyutinma(at)gmail(dot)com> |
---|---|
To: | Andre Piwoni <apiwoni(at)webmd(dot)net> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15638: pg_basebackup with --wal-method=stream incorrectly generates WAL segment created during backup |
Date: | 2019-02-21 18:28:03 |
Message-ID: | a079a3ee-f2f8-021a-595c-60dd3926f32e@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2/19/19 9:08 PM, Andre Piwoni wrote:
> By the way, you can assert this structure, including now explained
> diff in WAL segment taken during backup, for fetch vs stream WAL
> method by creating master and then creating new slave by taking base
> backup using both methods:
>
> pg_basebackup -h new_slave -D /var/lib/pgsql/10/data -v -P -R -U
> replication --wal-method=stream
> pg_basebackup -h new_slave -D /var/lib/pgsql/10/data -v -P -R -U
> replication --wal-method=fetch
I have verified on different versions of PostgreSQL the identity of
conflict segments received from master node and from pg_basebackup
--wal-method=stream. On PG11+ they are binary identical. However on PG10
and lower the segments are binary different. The logical content are the
same while meaningless tails differ.
In case of pg_basebackup --wal-method=fetch the segments are entirely
the same. And this case doesn't produce any problem in archiving.
I think the backup tools as well as custom archive scripts have to take
account of these points.
<http://www.webmdhealthservices.com/>
--
Regards,
Maksim Milyutin
From | Date | Subject | |
---|---|---|---|
Next Message | Andre Piwoni | 2019-02-21 18:57:32 | Re: BUG #15638: pg_basebackup with --wal-method=stream incorrectly generates WAL segment created during backup |
Previous Message | PG Bug reporting form | 2019-02-21 16:30:03 | BUG #15648: oracle_fdw extension not able to create |