Thanks Jim. Right now I just keep using the oid's - but it would be nice to eliminate the need for that completely.
UC On Tuesday 06 December 2005 15:01, Jim C. Nasby wrote: > 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. UC -- Open Source Solutions 4U, LLC 1618 Kelly St Phone: +1 707 568 3056 Santa Rosa, CA 95401 Cell: +1 650 302 2405 United States Fax: +1 707 568 6416 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster