| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
| Date: | 2009-02-09 15:44:17 |
| Message-ID: | 49904F51.5070005@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2009-02-09 15:49:32 | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
| Previous Message | Heikki Linnakangas | 2009-02-09 15:13:02 | Re: Hot standby, recovery infra |