Hi, On Fri, Mar 24, 2023 at 7:26 AM Tomas Vondra <tomas.von...@enterprisedb.com> wrote: > > I merged the earlier "fixup" patches into the relevant parts, and left > two patches with new tweaks (deducing the corrent "WAL" state from the > current state read by copy_sequence), and the interlock discussed here. >
Apart from that, how does the publication having sequences work with subscribers who are not able to handle sequence changes, e.g. in a case where PostgreSQL version of publication is newer than the subscriber? As far as I tested the latest patches, the subscriber (v15) errors out with the error 'invalid logical replication message type "Q"' when receiving a sequence change. I'm not sure it's sensible behavior. I think we should instead either (1) deny starting the replication if the subscriber isn't able to handle sequence changes and the publication includes that, or (2) not send sequence changes to such subscribers. Regards, -- Masahiko Sawada Amazon Web Services: https://aws.amazon.com
