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

From Michael Paquier
Subject Re: Error "initial slot snapshot too large" in create replication slot
Date
Msg-id Y0ZMN2ntvHW8mwgp@paquier.xyz
Whole thread Raw
In response to Re: Error "initial slot snapshot too large" in create replication slot  (Kyotaro Horiguchi <horikyota.ntt@gmail.com>)
Responses Re: Error "initial slot snapshot too large" in create replication slot  (Andres Freund <andres@anarazel.de>)
Re: Error "initial slot snapshot too large" in create replication slot  ("Gregory Stark (as CFM)" <stark.cfm@gmail.com>)
List pgsql-hackers
On Tue, Sep 13, 2022 at 05:31:05PM +0900, Kyotaro Horiguchi wrote:
> And ExportSnapshot repalces oversized subxip with overflowed.
>
> So even when GetSnapshotData() returns a snapshot with oversized
> subxip, it is saved as just "overflowed" on exporting. I don't think
> this is the expected behavior since such (no xip and overflowed)
> snapshot no longer works.
>
> On the other hand, it seems to me that snapbuild doesn't like
> takenDuringRecovery snapshots.
>
> So snapshot needs additional flag signals that xip is oversized and
> all xid are holded there. And also need to let takenDuringRecovery
> suggest subxip is oversized.

The discussion seems to have stopped here.  As this is classified as a
bug fix, I have moved this patch to next CF, waiting on author for the
moment.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Ankit Oza
Date:
Subject: Re: PostgreSQL Logical decoding
Next
From: Michael Paquier
Date:
Subject: Re: collect_corrupt_items_vacuum.patch