Horton
Menu

Re: IPC/MultixactCreation on the Standby server

Heikki Linnakangas <hlinnaka@iki.fi>

View thread
From: Heikki Linnakangas <hlinnaka@iki.fi>
To: Álvaro Herrera <alvherre@kurilemu.de>, pgsql-hackers <pgsql-hackers@lists.postgresql.org>, Andrey Borodin <x4mmm@yandex-team.ru>
Cc: Ivan Bykov <i.bykov@modernsys.ru>, Kirill Reshke <reshkekirill@gmail.com>
Date: 2025-11-27T07:20:24Z
Lists: pgsql-hackers 
On 26/11/2025 23:15, Álvaro Herrera wrote:
> On 2025-11-26, Heikki Linnakangas wrote:
> 
>> What happens if you replay the WAL generated with old binary, without
>> this patch, with new binary? It's not good:
> 
> Maybe this needs a new record identifier, separating old wal from that generated by the new code?

One downside of that is that the new WAL record type would be unreadable 
by older versions. We recommend upgrading standbys before primary, but 
it'd still be nicer if we could avoid that.

Maybe we can make RecordNewMultiXact() tolerate the missing page, in 
this special case of replaying WAL and the multixid being at the page 
boundary.

- Heikki

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Fix test to work with non-8kB block sizes

  2. Fix setting next multixid's offset at offset wraparound

  3. Add test for multixid wraparound

  4. Set next multixid's offset when creating a new multixid

  5. psql: Improve tab completion for large objects.

  6. Refactor some repetitive SLRU code

  7. Transaction IDs wrap around, per my proposal of 13-Aug-01. More