Re: pg_migrator and handling dropped columns
От | Peter Eisentraut |
---|---|
Тема | Re: pg_migrator and handling dropped columns |
Дата | |
Msg-id | 499532CC.5020702@gmx.net обсуждение исходный текст |
Ответ на | Re: pg_migrator and handling dropped columns (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_migrator and handling dropped columns
|
Список | pgsql-hackers |
Tom Lane wrote: >> 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. Note that pg_dump's output is already upgrade compatible. That's what pg_dump is often used for after all. I believe what we are after here is something like "in-place upgrade compatible" or "upgrade binary compatible". > And probably not even list it in the user documentation. I think we should still list it somewhere and say it is for use by in-place upgrade utilities. It will only confuse people if it is not documented at all.
В списке pgsql-hackers по дате отправления: