| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | Marko Kreen <markokr(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
| Date: | 2009-02-09 12:55:35 |
| Message-ID: | 20090209125535.GD25179@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 09, 2009 at 02:47:21PM +0200, Marko Kreen wrote:
> > That might be true but I know of apps that use them. Having the ability to
> > migrate those slowly by using SET WITHOUT OIDS is a Good Thing (tm).
>
> +1 for removal.
>
> Also, whether the removal happens or not, I would suggest a setting that
> makes Postgres accept, but ignore default_with_oids / WITH OIDS settings.
Err, you mean a setting that makes Postgres throw an error on the use
of WITH OIDS. Just silently ignoring the option is a fantastic way to
break applications silently.
Making pg_dump not output the WITH OIDS option on tables may be an
easier option.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2009-02-09 13:05:41 | Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS |
| Previous Message | David Lee Lambert | 2009-02-09 12:48:22 | Re: UUIDs using e2fs library on Linux in 8.4 |