Re: alter table .. reset not throwing an error if storage_parameter name is wrong

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
Cc: "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: alter table .. reset not throwing an error if storage_parameter name is wrong
Date: 2016-04-28 12:38:40
Message-ID: CAB7nPqQ_gkfNxHf2jdYZ6rLqT6ADkFkqnwh=4Y_Z1yfK+ifKJQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Thu, Apr 28, 2016 at 9:07 PM, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> wrote:
> I checked in PG 9.6 , if i provide any wrong storage parameter name while
> doing alter table , reset is not
> throwing an error :-
>
> \\throwing error , expected
> postgres=# alter table lon set (foo=10);
> ERROR: unrecognized parameter "foo"
>
> \\working ?
> postgres=# alter table lon reset (foo);
> ALTER TABLE

That's wanted this way for ages. RESET is an operation that does not
fail on a non-existing parameter.
--
Michael

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeffrey.Marshall 2016-04-28 13:28:28 BUG #14119: Database restore aborts with permission denied message
Previous Message tushar 2016-04-28 12:07:45 alter table .. reset not throwing an error if storage_parameter name is wrong