| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, 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-06 21:13:12 |
| Message-ID: | 200303062113.h26LDCP03630@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Tom Lane wrote:
> 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.
It would be good to somehow SET the use_oids GUC value on restore start,
and just use SET when the table is different than the default, but then
there is no mechanism to do that when you restore a single table.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-03-06 21:14:33 | Re: OIDs as keys |
| Previous Message | Bruce Momjian | 2003-03-06 21:11:05 | Re: OIDs as keys |