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 (view raw or flat )
Thread:
2005-12-01 17:01:05 from "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>
2005-12-01 17:25:22 from Richard Huxton <dev(at)archonet(dot)com>
2005-12-01 18:24:20 from Jaime Casanova <systemguards(at)gmail(dot)com>
2005-12-02 03:18:10 from "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>
2005-12-02 17:25:58 from Jaime Casanova <systemguards(at)gmail(dot)com>
2005-12-02 23:46:16 from "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
2005-12-02 23:58:39 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-12-03 02:22:57 from "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
2005-12-05 01:19:01 from "Greg Sabino Mullane" <greg(at)turnstep(dot)com>
2005-12-03 02:28:08 from "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
2005-12-03 23:07:19 from "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>
2005-12-06 23:01:20 from "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
2005-12-06 23:21:06 from "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>
2005-12-07 00:18:15 from Greg Stark <gsstark(at)mit(dot)edu>
2005-12-07 00:24:43 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-12-07 04:50:02 from Greg Stark <gsstark(at)mit(dot)edu>
2005-12-07 05:06:23 from Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
2005-12-08 07:13:15 from "Jim C(dot) Nasby" <jim(at)nasby(dot)net>
2005-12-01 20:37:09 from Martijn van Oosterhout <kleptog(at)svana(dot)org>
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
pgsql-hackers by date
Next :From: Jan WieckDate: 2005-12-02 23:58:47Subject : Re: Spam 508Previous :From : Tom LaneDate : 2005-12-02 23:53:46Subject : Re: strange behavior (corruption?) of large production database
pgsql-general by date
Next :From: Tom LaneDate: 2005-12-03 00:37:49Subject : Re: Reduce NUMERIC size by 2 bytes, reduce max length to 508 digits Previous :From : Tyler MacDonaldDate : 2005-12-02 23:53:20Subject : Re: memory leak under heavy load?
