Re: Error "initial slot snapshot too large" in create replication slot - Mailing list pgsql-hackers

From Dilip Kumar
Subject Re: Error "initial slot snapshot too large" in create replication slot
Date
Msg-id CAFiTN-sSbpHAvDg7gyaN5J2aaYEF4ycaSEAz0qfUJD_gM7n-eA@mail.gmail.com
Whole thread Raw
In response to Re: Error "initial slot snapshot too large" in create replication slot  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Tue, Sep 13, 2022 at 3:22 AM Andres Freund <andres@anarazel.de> wrote:

>
> It's not obvious to me that it's the right design (or even correct) to ask
> reorderbuffer about an xid being a subxid. Maybe I'm missing something, but
> why would reorderbuffer even be guaranteed to know about all these subxids?

Yeah, you are right, the reorderbuffer will only know about the
transaction for which changes got added to the reorder buffer.  So
this seems not to be the right design idea.

>
> I wonder if a better fix here wouldn't be to allow importing a snapshot with a
> larger ->xid array. Yes, we can't do that in CurrentSnapshotData, but IIRC we
> need to be in a transactional snapshot anyway, which is copied anyway?

Yeah when I first found this issue, I thought that should be the
solution.  But later it went in a different direction.

-- 
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson - v12
Next
From: Michael Paquier
Date:
Subject: Re: pg_upgrade generated files in subdir follow-up