Re: Error "initial slot snapshot too large" in create replication slot

Поиск
Список
Период
Сортировка
От Dilip Kumar
Тема Re: Error "initial slot snapshot too large" in create replication slot
Дата
Msg-id CAFiTN-sSbpHAvDg7gyaN5J2aaYEF4ycaSEAz0qfUJD_gM7n-eA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Error "initial slot snapshot too large" in create replication slot  (Andres Freund <andres@anarazel.de>)
Список 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 по дате отправления:

Предыдущее
От: Andres Freund
Дата:
Сообщение: Re: [RFC] building postgres with meson - v12
Следующее
От: Michael Paquier
Дата:
Сообщение: Re: pg_upgrade generated files in subdir follow-up