Re: ALTER DATABASE RESET with unexistent guc doesn't report an error - Mailing list pgsql-hackers

From Tom Lane
Subject Re: ALTER DATABASE RESET with unexistent guc doesn't report an error
Date
Msg-id 2612308.1757715167@sss.pgh.pa.us
Whole thread Raw
In response to Re: ALTER DATABASE RESET with unexistent guc doesn't report an error  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
I wrote:
> Looking at the patch, the delta in database.out raises
> another question:
>  ALTER DATABASE regression_tbd RENAME TO regression_utf8;
>  ALTER DATABASE regression_utf8 SET TABLESPACE regress_tblspace;
>  ALTER DATABASE regression_utf8 RESET TABLESPACE;
> +ERROR:  unrecognized configuration parameter "tablespace"
>  ALTER DATABASE regression_utf8 CONNECTION_LIMIT 123;
> The author of this bit of test script evidently thought that
> ALTER ... RESET TABLESPACE is the inverse of ALTER ... SET TABLESPACE,
> and what we are seeing is that it is not.  That may be a bug in
> itself, but it's not what Vitaly is on about, IIUC.

That was in fact a test bug, now corrected at 4adb0380b.
I've substituted a more on-point test case, wordsmithed the
comment a little bit, and pushed it.

Thanks for the report and patch!

            regards, tom lane



pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: PostgreSQL 18 GA press release draft
Next
From: Melanie Plageman
Date:
Subject: Re: RFC: extensible planner state