| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Removing special case OID generation |
| Date: | 2012-02-07 13:46:09 |
| Message-ID: | CA+U5nMJLc5KJJhqrmQuSjHtJcOGUNcUBkyubov4Zc6EBwQRJEg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Recent events have made me notice the OID handling.
AFAICS, OIDs are just a sequence with a max value that fits in a uint.
So ISTM that we should just strip out the OID handling code and just
have a system sequence defined like this
CREATE SEQUENCE _pg_oid
MINVALUE 0
MAXVALUE 4294967296
CACHE 8192
CYCLE;
Which would then make it easier to have a sequence for each toast
table and a sequence for lobs.
Not sure its important now, but maybe it will reduce the size of the
executable and avoid oid-specific bugs.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2012-02-07 13:56:52 | Re: semi-PoC: kNN-gist for cubes |
| Previous Message | Fujii Masao | 2012-02-07 13:10:09 | Re: incorrect handling of the timeout in pg_receivexlog |