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

From: Andres Freund <andres(at)anarazel(dot)de>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, jchampion(at)timescale(dot)com, y(dot)sokolov(at)postgrespro(dot)ru, dilipbalaut(at)gmail(dot)com, rjuju123(at)gmail(dot)com, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Error "initial slot snapshot too large" in create replication slot
Date: 2023-02-02 15:26:06
Message-ID: 20230202152606.ssmz46zzjxjt34b7@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On 2022-10-12 14:10:15 +0900, Michael Paquier wrote:
> 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.

FWIW, I view this more as lifting a limitation. I wouldn't want to
backpatch the change.

Greetings,

Andres Freund

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Reid Thompson 2023-02-02 15:41:55 Re: Add the ability to limit the amount of memory that can be allocated to backends.
Previous Message Justin Pryzby 2023-02-02 15:18:07 Re: Progress report of CREATE INDEX for nested partitioned tables