Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
От | Andrew Dunstan |
---|---|
Тема | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
Дата | |
Msg-id | 49904F51.5070005@dunslane.net обсуждение исходный текст |
Ответ на | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS (Marko Kreen <markokr@gmail.com>) |
Ответы |
Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
Список | pgsql-hackers |
Marko Kreen wrote: > But now that I learned that ALTER TABLE WITHOUT OIDS either causes bugs > or requires table rewrite, it turned from minor annoyance to big annoyance. > So I'd like have a reasonable path for getting rid of them, which we don't > have currently. Removing them completely is simplest path, but adding > extra features to support it is another. > > If we are talking about adding a feature, then I like retargeting > pg_dump --oids from data-only flag to apply to both data and schema. > Yes, this is incompatible change, but the change affects feature we > are discouraging anyway. > > How about a pg_dump flag that simply suppresses OIDs from the data and schema? cheers andrew
В списке pgsql-hackers по дате отправления: