diff options
| author | Michael Paquier <michael@paquier.xyz> | 2018-07-12 10:19:35 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2018-07-12 10:19:35 +0900 |
| commit | 9a7b7adc130a197e5c993a99e6aaa981f9341a35 (patch) | |
| tree | 79f81b20a80c672849b570ddc26af8c9bc7602c7 /src/backend/executor/nodeModifyTable.c | |
| parent | 39a96512b3ed72de7b24b2667d9575d7e9fcb326 (diff) | |
| download | postgresql-9a7b7adc130a197e5c993a99e6aaa981f9341a35.tar.gz postgresql-9a7b7adc130a197e5c993a99e6aaa981f9341a35.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