Re: pg_stat_get_replication_slot() marked not strict, crashes - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_stat_get_replication_slot() marked not strict, crashes
Date
Msg-id 631491.1648441062@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_stat_get_replication_slot() marked not strict, crashes  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
Andres Freund <andres@anarazel.de> writes:
> On 2022-03-28 08:28:29 +0530, Amit Kapila wrote:
>> I am not sure if for 14 we can make a catalog change as that would
>> require catversion bump, so adding a code-level check as suggested by
>> Andres seems like a better option. Andres/Tom, any better ideas for
>> this?

> I think we could do the catalog change too, so that future initdb's are marked
> correctly. But we obviously do need the code-level check nevertheless.

Yeah.  We have to install the C-level check, so I don't see any
point in changing the catalogs in back branches.  That'll create
confusion while not saving anything.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: pg_stat_get_replication_slot() marked not strict, crashes
Next
From: Michael Paquier
Date:
Subject: Re: Preventing indirection for IndexPageGetOpaque for known-size page special areas