Re: IPC/MultixactCreation on the Standby server

2025-06-25 Thread Dmitry
On 25.06.2025 12:34, Andrey Borodin wrote: On 25 Jun 2025, at 11:11, Dmitry wrote: #6 GetMultiXactIdMembers (multi=45559845, members=0x7ffdaedc84b0, from_pgupgrade=, isLockOnly=) at /usr/src/postgresql-17-17.5-1.pgdg24.04+1/build/../src/backend/access/transam/multixact.c:1483

Re: IPC/MultixactCreation on the Standby server

2025-06-25 Thread Andrey Borodin
> On 25 Jun 2025, at 11:11, Dmitry wrote: > > #6 GetMultiXactIdMembers (multi=45559845, members=0x7ffdaedc84b0, > from_pgupgrade=, isLockOnly=) > at > /usr/src/postgresql-17-17.5-1.pgdg24.04+1/build/../src/backend/access/transam/multixact.c:1483 Hi Dmitry! This looks to be rela

IPC/MultixactCreation on the Standby server

2025-06-24 Thread Dmitry
Hi, hackers The problem is as follows. A replication cluster includes a primary server and one hot-standby replica. The workload on the primary server is represented by multiple requests generating multixact IDs, while the hot-standby replica performs reading requests. After some time, all re