mirror of
https://github.com/postgres/postgres.git
synced 2025-07-02 09:02:37 +03:00
In successful pg_recvlogical, end PGRES_COPY_OUT cleanly.
pg_recvlogical merely called PQfinish(), so the backend sent messages
after the disconnect. When that caused EPIPE in internal_flush(),
before a LogicalConfirmReceivedLocation(), the next pg_recvlogical would
repeat already-acknowledged records. Whether or not the defect causes
EPIPE, post-disconnect messages could contain an ErrorResponse that the
user should see. One properly ends PGRES_COPY_OUT by repeating
PQgetCopyData() until it returns a negative value. Augment one of the
tests to cover the case of WAL past --endpos. Back-patch to v10, where
commit 7c030783a5
first appeared. Before
that commit, pg_recvlogical never reached PGRES_COPY_OUT.
Reported by Thomas Munro.
Discussion: https://postgr.es/m/CAEepm=1MzM2Z_xNe4foGwZ1a+MO_2S9oYDq3M5D11=JDU_+0Nw@mail.gmail.com
This commit is contained in:
@ -71,6 +71,11 @@ my $endpos = $node_master->safe_psql('postgres',
|
||||
);
|
||||
print "waiting to replay $endpos\n";
|
||||
|
||||
# Insert some rows after $endpos, which we won't read.
|
||||
$node_master->safe_psql('postgres',
|
||||
qq[INSERT INTO decoding_test(x,y) SELECT s, s::text FROM generate_series(5,50) s;]
|
||||
);
|
||||
|
||||
my $stdout_recv = $node_master->pg_recvlogical_upto(
|
||||
'postgres', 'test_slot', $endpos, 180,
|
||||
'include-xids' => '0',
|
||||
@ -89,7 +94,7 @@ $stdout_recv = $node_master->pg_recvlogical_upto(
|
||||
'skip-empty-xacts' => '1');
|
||||
chomp($stdout_recv);
|
||||
is($stdout_recv, '',
|
||||
'pg_recvlogical acknowledged changes, nothing pending on slot');
|
||||
'pg_recvlogical acknowledged changes');
|
||||
|
||||
$node_master->safe_psql('postgres', 'CREATE DATABASE otherdb');
|
||||
|
||||
|
Reference in New Issue
Block a user