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

2025-09-11 Thread Kirill Reshke
Hi! On Thu, 11 Sept 2025 at 13:35, Vitaly Davydov 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

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

2025-09-11 Thread Tom Lane
=?utf-8?Q?=C3=81lvaro?= Herrera writes: > On 2025-Sep-11, Kirill Reshke wrote: >> I think we can remove "support" for ALTER DATABASE RESET TABLESPACE. > What about ALTER USER RESET TABLESPACE? Yeah, I think you're right. The complaint is fundamentally that these two cases behave differently: r

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

2025-09-11 Thread Álvaro Herrera
On 2025-Sep-11, Kirill Reshke wrote: > I think we can remove "support" for ALTER DATABASE RESET TABLESPACE. What about ALTER USER RESET TABLESPACE? -- Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/ "Computing is too important to be left to men." (Karen Spärck Jone

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

2025-09-11 Thread Vitaly Davydov
Dear Hackers, I've found that ALTER DATABASE RESET with an unexistent guc does nothing without error reporting. ALTER DATABASE SET reports an error if guc doesn't exist: > alter database mydb set myparam to 10; ERROR: unrecognized configuration parameter "myparam" ALTER DATABASE RESET doesn't