diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2020-10-14 20:12:26 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2020-10-14 20:12:26 -0300 |
| commit | 4e9821b6fac5042e872d5397f711a67984b165f8 (patch) | |
| tree | 805886d73e19331696339de5aa94e6cdefc3808b /contrib/test_decoding/test_decoding.c | |
| parent | b94109ce375b137f235149bfba3559c69f4573e7 (diff) | |
| download | postgresql-4e9821b6fac5042e872d5397f711a67984b165f8.tar.gz postgresql-4e9821b6fac5042e872d5397f711a67984b165f8.zip | |
Restore replication protocol's duplicate command tags
I removed the duplicate command tags for START_REPLICATION inadvertently
in commit 07082b08cc5d, but the replication protocol requires them. The
fact that the replication protocol was broken was not noticed because
all our test cases use an optimized code path that exits early, failing
to verify that the behavior is correct for non-optimized cases. Put
them back.
Also document this protocol quirk.
Add a test case that shows the failure. It might still succeed even
without the patch when run on a fast enough server, but it suffices to
show the bug in enough cases that it would be noticed in buildfarm.
Author: Álvaro Herrera <alvherre@alvh.no-ip.org>
Reported-by: Henry Hinze <henry.hinze@gmail.com>
Reviewed-by: Petr Jelínek <petr.jelinek@2ndquadrant.com>
Discussion: https://postgr.es/m/16643-eaadeb2a1a58d28c@postgresql.org
Diffstat (limited to 'contrib/test_decoding/test_decoding.c')
0 files changed, 0 insertions, 0 deletions