Re: WIP: fix SET WITHOUT OIDS, add SET WITH OIDS

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: David Fetter <david(at)fetter(dot)org>
Cc: 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 02:32:36
Message-ID: 498F95C4.2030806@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Fetter wrote:
> On Sun, Feb 08, 2009 at 11:51:22AM -0500, Tom Lane wrote:
>
>> Now, if you want to argue that we should get rid of SET WITHOUT OIDS
>> altogether,
>>
>
> +1 for removing it altogether. Row OIDs are and ugly wart :P
>
>
>

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).

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2009-02-09 02:37:16 Re: 64 bit PostgreSQL 8.3.6 build on AIX 5300-09-02-0849 with IBM XL C/C++ 10.1.0.1 - initdb fails (could not dump unrecognized node type: 650)
Previous Message Fujii Masao 2009-02-09 02:23:25 Re: Synch Replication