Re: pg_migrator and handling dropped columns

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pg_migrator and handling dropped columns
Дата
Msg-id 14562.1234463946@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pg_migrator and handling dropped columns  (Bruce Momjian <bruce@momjian.us>)
Ответы Re: pg_migrator and handling dropped columns  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: pg_migrator and handling dropped columns  (Bruce Momjian <bruce@momjian.us>)
Re: pg_migrator and handling dropped columns  (Peter Eisentraut <peter_e@gmx.net>)
Список pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> Tom Lane wrote:
>> (4) add a switch to pg_dump to include dropped columns in its
>> schema output and then drop them.  This seems far more maintainable
>> than writing separate code that tries to parse the output.

> I assume I would also drop the column in the pg_dump output.  

Right, that's what I meant --- do all the work within pg_dump.

> Is this acceptable to everyone?  We could name the option
> -u/--upgrade-compatible.

If the switch is specifically for pg_upgrade support (enabling this as
well as any other hacks we find necessary), which seems like a good
idea, then don't chew up a short option letter for it.  There should be
a long form only.  And probably not even list it in the user
documentation.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: DISCARD ALL failing to acquire locks on pg_listen
Следующее
От: "Joshua D. Drake"
Дата:
Сообщение: Re: pg_migrator and handling dropped columns