Re: 8.1, OID's and plpgsql

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
Cc: "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: 8.1, OID's and plpgsql
Date: 2005-12-02 23:58:39
Message-ID: 9093.1133567919@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Jim C. Nasby" <jim(at)nasby(dot)net> writes:
> Maybe the docs should be changed to just say that you should never reuse
> a ctid outside of the transaction you obtained the ctid in?

That's not a sufficient rule either: someone else could still delete or
update the row while your transaction runs. You'd really have to SELECT
FOR UPDATE or FOR SHARE to be sure the ctid remains stable. (Of course,
this isn't an issue for the case of a row you just inserted yourself,
since no one else can see it yet to change it.)

The paragraph defining ctid is not the place for a discussion of how it
could be used ... I'm not quite sure where is, though.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2005-12-03 00:37:49 Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 digits
Previous Message Tyler MacDonald 2005-12-02 23:53:20 Re: memory leak under heavy load?

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan Wieck 2005-12-02 23:58:47 Re: Spam 508
Previous Message Tom Lane 2005-12-02 23:53:46 Re: strange behavior (corruption?) of large production database