diff options
| author | Michael Paquier <michael@paquier.xyz> | 2018-07-12 10:19:51 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2018-07-12 10:19:51 +0900 |
| commit | 0414ac6a1eb2e457c8019c5a558bd72b37dede89 (patch) | |
| tree | 6f89c7e1ba5a5781eb183ba9e531e1af828c1879 /src/backend/executor/nodeModifyTable.c | |
| parent | 5b762d96e8c602434bc7e56f910c23c54e95f80d (diff) | |
| download | postgresql-0414ac6a1eb2e457c8019c5a558bd72b37dede89.tar.gz postgresql-0414ac6a1eb2e457c8019c5a558bd72b37dede89.zip | |
Make logical WAL sender report streaming state appropriately
WAL senders sending logically-decoded data fail to properly report in
"streaming" state when starting up, hence as long as one extra record is
not replayed, such WAL senders would remain in a "catchup" state, which
is inconsistent with the physical cousin.
This can be easily reproduced by for example using pg_recvlogical and
restarting the upstream server. The TAP tests have been slightly
modified to detect the failure and strengthened so as future tests also
make sure that a node is in streaming state when waiting for its
catchup.
Backpatch down to 9.4 where this code has been introduced.
Reported-by: Sawada Masahiko
Author: Simon Riggs, Sawada Masahiko
Reviewed-by: Petr Jelinek, Michael Paquier, Vaishnavi Prabakaran
Discussion: https://postgr.es/m/CAD21AoB2ZbCCqOx=bgKMcLrAvs1V0ZMqzs7wBTuDySezTGtMZA@mail.gmail.com
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions