Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view
Дата
Msg-id 14241.1307461282@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-bugs
Robert Haas <robertmhaas@gmail.com> writes:
> If your point here is that you don't want to spend time hacking on
> this because it's a fairly marginal feature and therefore not terribly
> high on your priority list, I can understand that.  But if you're
> actually defending the current implementation, I'm going to have to
> respectfully disagree.  It's broken, and it sucks, and this is not the
> first complaint we've had about it.

The spec's definition of USING is broken and sucky, and we're
implementing it as best we can.  I don't feel a need to invent
strange nonstandard behavior to work around the fact that USING
is fragile *by definition*.  Complain to the standards committee
about that.

(Question: would you also have us try to work around the fact that
USING stops working if you rename one of the join columns?)

            regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: ON DELETE CASCADE with multiple paths in PostgreSQL 9.x
Следующее
От: Daniel Cristian Cruz
Дата:
Сообщение: Re: BUG #6050: Dump and restore of view after a schema change: can't restore the view