[PostgreSQL-Hackers] deprecating the use of OIDs

[PostgreSQL-Hackers] deprecating the use of OIDs

	Greg Sabino Mullane
	Sep 29, 2003 at 10:18 pm

I think most people on this list will agree that having OIDs on user
tables is a Bad Thing. For some previous discussion of why, see:
...
Objections, comments, etc. are welcome.

The GUC route sounds good. I'd like to see ctid handling beefed up at the
same time. For example, some operators such as != would be nice and might
ease the pain a little for people used to using oids as their "tuple id" :)

- --
Greg Sabino Mullane greg@turnstep.com
PGP Key: 0x14964AC8 200309291818

Search Discussions

Discussion Posts

Neil Conway: I think most people on this list will agree that having OIDs on user tables is a Bad Thing. For some previous discussion of why, see: http://www.mail-archive.com/pgsql-hackers@postgresql.org/msg27374.html My understanding of the conclusion of previous discussions on this topic is that getting rid of OIDs on user tables eventually would be good, but there is some disagreement / confusion on how exactly to manage the transition. I think we should do the following for 7.5: (1) Add a GUC var, with

Follow ups

Related Discussions

Discussion Navigation

view	thread \| post
posts	‹ prev \| 2 of 8 \| next ›

Discussion Overview

group	pgsql-hackers @
categories	postgresql
posted	Sep 29, '03 at 9:34p
active	Sep 29, '03 at 11:51p
posts	8
users	4
website	postgresql.org...
irc	#postgresql

font	variable	Hotkey: f
user style	avatars	Hotkey: a

[PostgreSQL-Hackers] deprecating the use of OIDs

Search Discussions

Discussion Posts

Related Discussions

4 users in discussion