| From: | Neil Conway <neilc(at)samurai(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: deprecating the use of OIDs |
| Date: | 2003-09-29 22:41:42 |
| Message-ID: | 1064875302.22627.2.camel@tokyo |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 2003-09-29 at 18:37, Tom Lane wrote:
> It doesn't seem to me that this really buys much. What we really want
> is a way for a dump/reload to remove OIDs from tables that formerly had
> them; otherwise people will not easily be able to migrate their existing
> tables away from having OIDs.
Can't they just use ALTER TABLE ... WITHOUT OIDS?
> > ... and a single SET can apply to
> > multiple CREATE TABLEs.
>
> Not unless you want partial pg_restores to break.
So is it worth doing this rather than WITH/WITHOUT OIDS, then?
-Neil
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephan Szabo | 2003-09-29 22:55:04 | Re: ADD FOREIGN KEY (was Re: [GENERAL] 7.4Beta) |
| Previous Message | Tom Lane | 2003-09-29 22:37:12 | Re: deprecating the use of OIDs |