Re: logical decoding and replication of sequences, take 2
Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
From: Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>
To: Tomas Vondra <tomas.vondra@enterprisedb.com>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>, Masahiko Sawada <sawada.mshk@gmail.com>,
Amit Kapila <amit.kapila16@gmail.com>, Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Date: 2023-07-14T14:02:27Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Migrate logical slots to the new node during an upgrade.
- 29d0a77fa660 17.0 cited
-
Make test_decoding ddl.out shorter
- d6677b93c79b 17.0 landed
- c5c5832600e9 14.9 landed
- b1dc946eee3d 16.0 landed
- 3bb8b9342f8a 15.4 landed
-
Fix snapshot handling in logicalmsg_decode
- 949ac32e1267 15.3 landed
- 8b9cbd42b61f 14.8 landed
- 4df581fa0f4b 13.11 landed
- 497f863f0598 12.15 landed
- 8de91ebf2ac1 11.20 landed
- 7fe1aa991b62 16.0 landed
-
doc: Adjust a few more references to "postmaster"
- 17e72ec45d31 16.0 cited
-
Revert "Logical decoding of sequences"
- 2c7ea57e56ca 15.0 cited
On Fri, Jul 14, 2023 at 4:10 PM Tomas Vondra <tomas.vondra@enterprisedb.com> wrote: > > I don't think that's true - this will create 1 record with > "created=true" (the one right after the CREATE SEQUENCE) and the rest > will have "created=false". I may have misread the code. > > I realized I haven't modified seq_desc to show this flag, so I did that > in the updated patch version, which makes this easy to see. Now I see it. Thanks for the clarification. > > > > Am I missing something here? > > > > You're missing the fact that pg_upgrade does not copy replication slots, > so the restart_lsn does not matter. > > (Yes, this is pretty annoying consequence of using pg_upgrade. And maybe > we'll improve that in the future - but I'm pretty sure we won't allow > decoding old WAL.) Ah, I see. Thanks for correcting me. > >>> > >> > >> Hmmmm, that might work. I feel a bit uneasy about having to keep all > >> relfilenodes, not just sequences ... > > > > From relfilenode it should be easy to get to rel and then see if it's > > a sequence. Only add relfilenodes for the sequence. > > > > Will try. > Actually, adding all relfilenodes to hash may not be that bad. There shouldn't be many of those. So the extra step to lookup reltype may not be necessary. What's your reason for uneasiness? But yeah, there's a way to avoid that as well. Should I wait for this before the second round of review? -- Best Wishes, Ashutosh Bapat