Re: [GENERAL] 8.1, OID's and plpgsql - Mailing list pgsql-hackers

From Jim C. Nasby
Subject Re: [GENERAL] 8.1, OID's and plpgsql
Date
Msg-id 20051206230120.GR16053@nasby.net
Whole thread Raw
Responses Re: [GENERAL] 8.1, OID's and plpgsql  (Greg Stark <gsstark@mit.edu>)
Re: [GENERAL] 8.1, OID's and plpgsql  ("Uwe C. Schroeder" <uwe@oss4u.com>)
List pgsql-hackers
On Sat, Dec 03, 2005 at 03:07:19PM -0800, Uwe C. Schroeder wrote:
> the ctid seems to be the solution to my problem. I'm inserting the record in a 
> transaction so the ctid shouldn't change while the transaction isn't finished 
> (either rolled back or committed).
> One question though. How would I get the ctid of the just inserted record. GET 
> DIAGNOSTICS only handles row count and oid per the docs.

Right now you don't. :( ISTM there should be a way to get back the row
you just inserted. Whether a ctid is the right way to do that I don't
know...

I'm going to move this over to -hackers to see what people over there
have to say.
-- 
Jim C. Nasby, Sr. Engineering Consultant      jnasby@pervasive.com
Pervasive Software      http://pervasive.com    work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf       cell: 512-569-9461


pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: more locale problems on Windows
Next
From: "Marc G. Fournier"
Date:
Subject: Re: Slow email caught in the act