Re: OIDs, CTIDs, updateable cursors and friends - Mailing list pgsql-hackers

From Zeugswetter Andreas SB SD
Subject Re: OIDs, CTIDs, updateable cursors and friends
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA40184CFDB@m0114.s-mxs.net
Whole thread Raw
In response to OIDs, CTIDs, updateable cursors and friends  (Shachar Shemesh <psql@shemesh.biz>)
Responses Re: OIDs, CTIDs, updateable cursors and friends
List pgsql-hackers
> I believe the ODBC driver uses CTID for this sort of problem.  CTID is
> guaranteed to exist and to be fast to access (since it's a physical
> locator).  Against this you have the problem that concurrent updates
> of the record will move it, leaving your CTID invalid.  However, that

IIRC the ctid access follows the chain up to the currently valid
tuple ? I thought the only enemy of ctid access was "vacuum" ?

Andreas


pgsql-hackers by date:

Previous
From: "Thomas Hallgren"
Date:
Subject: Re: Advice regarding configuration parameters
Next
From: "Zeugswetter Andreas SB SD"
Date:
Subject: Re: [PATCHES] NO WAIT ...