| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> |
| Cc: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>, "Shachar Shemesh" <psql(at)shemesh(dot)biz>, "Hackers" <pgsql-hackers(at)postgresql(dot)org>, "PostgreSQL OLE DB development" <oledb-dev(at)gborg(dot)postgresql(dot)org> |
| Subject: | Re: OIDs, CTIDs, updateable cursors and friends |
| Date: | 2004-02-19 16:01:14 |
| Message-ID: | 2262.1077206474@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Zeugswetter Andreas SB SD" <ZeugswetterA(at)spardat(dot)at> writes:
> IIRC the ctid access follows the chain up to the currently valid
> tuple ?
No.
I think Hiroshi or someone put in a function you can use to follow the
chain, but a simple "WHERE ctid = whatever" won't do it. In any case,
if you're not holding an open transaction then you have to be prepared
to have the dead tuple vacuumed out from under you, in which case you'd
not be able to follow the chain anyway.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-02-19 16:01:48 | Re: [PATCHES] NO WAIT ... |
| Previous Message | Zeugswetter Andreas SB SD | 2004-02-19 15:33:34 | Re: [PATCHES] NO WAIT ... |