| From: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: OID wraparound (was Re: pg_depend) |
| Date: | 2001-07-18 20:10:13 |
| Message-ID: | 01071816101306.00973@lowen.wgcr.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wednesday 18 July 2001 16:06, Tom Lane wrote:
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> > Is the idea to make oid's optional, with them disabled by default on
> > user tables?
> It remains to be debated exactly how users should control the choice for
> user tables, and which choice ought to be the default. I don't have a
> strong opinion about that either way, and am prepared to hear
> suggestions.
SET OIDGEN boolean for database-wide default policy.
CREATE TABLE WITH OIDS for individual tables? CREATE TABLE WITHOUT OIDS?
?? Is this sort of thing addressed by any SQL standard (Thomas?)?
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Myers | 2001-07-18 20:14:50 | Re: MySQL Gemini code |
| Previous Message | Bruce Momjian | 2001-07-18 20:08:31 | Re: OID wraparound (was Re: pg_depend) |