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: | Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'pgsql-hackers(at)postgreSQL(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: AW: [HACKERS] Getting OID in psql of recent insert |
Date: | 1999-11-22 19:37:54 |
Message-ID: | 199911221937.OAA09122@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Zeugswetter Andreas SEV <ZeugswetterA(at)wien(dot)spardat(dot)at> writes:
> >> Yes, I use 'em the same way. I think an OID is kind of like a pointer
> >> in a C program: good for fast, unique access to an object within the
> >> context of the execution of a particular application (and maybe not
> >> even that long). You don't write pointers into files to be used again
> >> by other programs, though, and in the same way an OID isn't a good
> >> candidate for a long-lasting reference from one table to another.
>
> > I thought this special case is where the new xid access method would come
> > in.
>
> Good point, but (AFAIK) you could only use it for tables that you were
> sure no other client was updating in parallel. Otherwise you might be
> updating a just-obsoleted tuple. Or is there a solution for that?
>
> > Is someone still working on the xid access ?
>
> I think we have the ability to refer to CTID in WHERE now, but not yet an
> access method that actually makes it fast...
Hiroshi supplied a patch to allow it in the executor, and I applied it.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Meskes | 1999-11-22 21:06:16 | Float/Numeric? |
Previous Message | Tom Lane | 1999-11-22 19:15:39 | Re: [HACKERS] Re: postgres RPM build on Suse linux 6.2 |