Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist - Mailing list pgsql-bugs

From Nathan Bossart
Subject Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
Date
Msg-id aIfoWKXanBNGhdwt@nathan
Whole thread Raw
In response to Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist  (Nathan Bossart <nathandbossart@gmail.com>)
Responses Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist
List pgsql-bugs
On Fri, Jul 25, 2025 at 09:15:17AM -0500, Nathan Bossart wrote:
> On Thu, Jul 24, 2025 at 11:06:57PM +0200, Laurenz Albe wrote:
>> Anyway, I'll mark the patch as "ready for committer".
> 
> Thanks.  I'd like to get this fixed in the August releases, so I'm planning
> to commit this sometime late next week, barring additional feedback or
> objections.

I looked into how easily this back-patched to v15 (where commit 88103567c
was added), and I noticed that the ALTER SYSTEM code looks a bit different
on v15 and v16.  Furthermore, I didn't see a simple way to fix it on those
versions without first back-patching commit 2d870b4.  From the commit
message, it looks like Tom didn't back-patch it at the time due to a lack
of complaints.  I'm currently thinking we should first back-patch that one
to at least v15, if not all supported versions, before applying my proposed
patch.  Thoughts?

-- 
nathan



pgsql-bugs by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: Postgres: Queries are too slow after upgrading to PG17 from PG15
Next
From: Tom Lane
Date:
Subject: Re: BUG #18964: `ALTER DATABASE ... RESET ...` fails to reset extension parameters that no longer exist