Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Date
Msg-id 20090209125535.GD25179@svana.org
Whole thread Raw
In response to Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS  (Marko Kreen <markokr@gmail.com>)
Responses Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
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  (Marko Kreen <markokr@gmail.com>)
List 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@svana.org>   http://svana.org/kleptog/
> Please line up in a tree and maintain the heap invariant while
> boarding. Thank you for flying nlogn airlines.

pgsql-hackers by date:

Previous
From: Marko Kreen
Date:
Subject: Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS
Next
From: Heikki Linnakangas
Date:
Subject: Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS