| From: | Marti Raudsepp <marti(at)juffo(dot)org> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Jim Nasby <jim(at)nasby(dot)net>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Removing special case OID generation |
| Date: | 2012-02-13 13:51:16 |
| Message-ID: | CABRT9RAOjO3fYSgH+eJcPLhJa70OXKcFSXnYDm40x9XCK1CnyA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Feb 13, 2012 at 15:08, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> Honestly, I think the biggest hassle of the OID code is not so much
> the way they're generated as the way they're stored within heap
> tuples. I've wondered whether we should go through the system
> catalogs and replace all of the hidden OID columns with a normal
> column called "oid" of type OID
Do we have a clear idea about what to do with user tables that are
created WITH OIDS? Do we care about compatibility with that at all? Do
we generate this explicit "oid" column manually or do we just tell
users to use a serial or global sequence instead?
Personally I'd also like to see us get rid of the default_with_oids
setting -- I assume the existence of that is the reason why pgAdmin
and TOAD still generate table DDL with an explicit "WITH (OIDS=FALSE)"
Regards,
Marti
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2012-02-13 14:18:19 | Re: Removing special case OID generation |
| Previous Message | Robert Haas | 2012-02-13 13:48:06 | Re: Bugs/slowness inserting and indexing cubes |