Re: OIDs as keys

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, daniel alvarez <d-alvarez(at)gmx(dot)de>, Richard Huxton <dev(at)archonet(dot)com>, PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: OIDs as keys
Date: 2003-03-05 15:20:40
Message-ID: 19293.1046877640@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Neil Conway <neilc(at)samurai(dot)com> writes:
> Rather than specifying the use of OIDs by WITH OIDS clauses for each
> CREATE TABLE in a dump, couldn't we do it by adding a SET command that
> toggles the 'use_oids' GUC option prior to every CREATE TABLE?

Seems better than cluttering the CREATE TABLE itself with them, I guess.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Richard Huxton 2003-03-05 16:12:09 Re: Planner matching constants across tables in a join
Previous Message Tom Lane 2003-03-05 15:08:38 Re: Planner matching constants across tables in a join