Re: Is this a bug?

Поиск
Список
Период
Сортировка
От Fabrízio de Royes Mello
Тема Re: Is this a bug?
Дата
Msg-id CAFcNs+qH8P9Sgn57QGb+Gu3MVXRYR7oM0uAC9i51MzHjrsGnFA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: Is this a bug?  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: Is this a bug?  (Michael Paquier <michael.paquier@gmail.com>)
Список pgsql-hackers

On Thu, Mar 13, 2014 at 10:22 AM, Robert Haas <robertmhaas@gmail.com> wrote:
>
> On Wed, Mar 12, 2014 at 11:11 PM, Fabrízio de Royes Mello
> <fabriziomello@gmail.com> wrote:
> > Hi all,
> >
> > Shouldn't the "ALTER" statements below raise an exception?
> >
> > fabrizio=# CREATE TABLE foo(bar SERIAL PRIMARY KEY);
> > CREATE TABLE
> >
> > fabrizio=# SELECT relname, reloptions FROM pg_class WHERE relname ~ '^foo';
> >    relname   | reloptions
> > -------------+------------
> >  foo         |
> >  foo_bar_seq |
> >  foo_pkey    |
> > (3 rows)
> >
> > fabrizio=# ALTER TABLE foo RESET (noname);
> > ALTER TABLE
> >
> > fabrizio=# ALTER INDEX foo_pkey RESET (noname);
> > ALTER INDEX
> >
> > fabrizio=# ALTER TABLE foo ALTER COLUMN bar RESET (noname);
> > ALTER TABLE
> >
> >
> > If I try to "SET" an option called "noname" obviously will raise an
> > exception:
> >
> > fabrizio=# ALTER TABLE foo SET (noname=1);
> > ERROR:  unrecognized parameter "noname"
>
> Well, it's fairly harmless, but it might not be a bad idea to tighten that up.
>

The attached patch tighten that up.

Grettings,

--
Fabrízio de Royes Mello
Consultoria/Coaching PostgreSQL
>> Timbira: http://www.timbira.com.br
>> Blog sobre TI: http://fabriziomello.blogspot.com
>> Perfil Linkedin: http://br.linkedin.com/in/fabriziomello
>> Twitter: http://twitter.com/fabriziomello
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: commit fest 2014-01 closed
Следующее
От: Joe Conway
Дата:
Сообщение: Re: pg_dump without explicit table locking