| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [GENERAL] 8.1, OID's and plpgsql |
| Date: | 2005-12-06 23:01:20 |
| Message-ID: | 20051206230120.GR16053@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general 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(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-12-06 23:04:04 | Re: deadlock on the same relation |
| Previous Message | Carlos Correia | 2005-12-06 22:53:23 | Re: Graphical modelling tool |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Uwe C. Schroeder | 2005-12-06 23:21:06 | Re: [GENERAL] 8.1, OID's and plpgsql |
| Previous Message | Andrew Dunstan | 2005-12-06 22:07:17 | Re: more locale problems on Windows |