Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created
Дата
Msg-id 11221.1341069176@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created  (Bruce Momjian <bruce@momjian.us>)
Список pgsql-bugs
Bruce Momjian <bruce@momjian.us> writes:
> On Fri, Jun 29, 2012 at 11:35:15PM -0400, Tom Lane wrote:
>> I think you're misjudging the core of the issue.  The same thing
>> would happen if somebody dropped and recreated the public schema.
>> Or anything else that we create at initdb time but allow to be
>> dropped.

> I just tested dropping and recreating the 'public' schema and pg_upgrade
> worked fine.

Did it restore the nonstandard ownership of the schema?  Your proposed
fix for plpgsql won't preserve the previous state of the extension.
(Maybe we don't care, but it needs consideration.)

            regards, tom lane

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

Предыдущее
От: miroslav.sulc@fordfrog.com
Дата:
Сообщение: BUG #6712: PostgreSQL 9.2 beta2: alter table drop constraint does not work on inherited master table
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: BUG #6706: pg_upgrade fails when plpgsql dropped/re-created