Re: pg_stat_get_replication_slot() marked not strict, crashes
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andres Freund <andres@anarazel.de>
Cc: Amit Kapila <amit.kapila16@gmail.com>, vignesh C <vignesh21@gmail.com>,
Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2022-03-28T04:17:42Z
Lists: 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
Commits
-
Mark pg_stat_get_subscription_stats() strict.
- da4b56662f2c 15.0 landed
-
Fix NULL input behaviour of pg_stat_get_replication_slot().
- 43a7dc96eb36 15.0 landed
- c1a0d7d1c4b7 14.3 landed