Re: ALTER DATABASE RESET with unexistent guc doesn't report an error

From: Kirill Reshke <reshkekirill(at)gmail(dot)com>
To: Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER DATABASE RESET with unexistent guc doesn't report an error
Date: 2025-09-11 12:07:29
Message-ID: CALdSSPgHHM0RS7PRPp=8oXjWr4OB0COFhOZtWZ10O-gttfPh+Q@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi!

On Thu, 11 Sept 2025 at 13:35, Vitaly Davydov <v(dot)davydov(at)postgrespro(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christoph Berg 2025-09-11 12:28:06 Re: A failure in 031_recovery_conflict.pl on Debian/s390x
Previous Message Christoph Berg 2025-09-11 11:39:21 Re: pgsql: Introduce pg_shmem_allocations_numa view