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

From Kirill Reshke
Subject Re: ALTER DATABASE RESET with unexistent guc doesn't report an error
Date
Msg-id CALdSSPgHHM0RS7PRPp=8oXjWr4OB0COFhOZtWZ10O-gttfPh+Q@mail.gmail.com
Whole thread Raw
In response to ALTER DATABASE RESET with unexistent guc doesn't report an error  ("Vitaly Davydov" <v.davydov@postgrespro.ru>)
Responses Re: ALTER DATABASE RESET with unexistent guc doesn't report an error
List pgsql-hackers
Hi!

On Thu, 11 Sept 2025 at 13:35, Vitaly Davydov <v.davydov@postgrespro.ru> wrote:
> I've also think that ALTER DATABASE RESET TABLESPACE does
> nothing without any error reporting.

I can see that ALTER DATABASE RESET TABLESPACE indeed does not change
dattablespace.
Documentation also lacks any information about support of something
like this. [0]

This test case looks like just an oversight of 0844b3968985
I think we can remove "support" for ALTER DATABASE RESET TABLESPACE.

LGTM


[0] https://www.postgresql.org/docs/current/sql-alterdatabase.html


-- 
Best regards,
Kirill Reshke



pgsql-hackers by date:

Previous
From: Christoph Berg
Date:
Subject: Re: pgsql: Introduce pg_shmem_allocations_numa view
Next
From: Christoph Berg
Date:
Subject: Re: A failure in 031_recovery_conflict.pl on Debian/s390x