| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org, "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
| Subject: | Re: Lazy xid assignment V4 |
| Date: | 2007-09-05 21:35:04 |
| Message-ID: | 25176.1189028104@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
Robert Treat <xzilla(at)users(dot)sourceforge(dot)net> writes:
> ISTM that by removing the transaction column, there is no way to see the XID
> for relations thats have been updated (which by definition will have locks on
> them). Am I mis-reading the docs, or have we lost that functionality?
Huh? What do you mean by "XID for relations that have been updated"?
Relations don't have XIDs.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2007-09-05 21:49:58 | Re: Lazy xid assignment V4 |
| Previous Message | Robert Treat | 2007-09-05 21:27:31 | Re: Lazy xid assignment V4 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2007-09-05 21:49:58 | Re: Lazy xid assignment V4 |
| Previous Message | Robert Treat | 2007-09-05 21:27:31 | Re: Lazy xid assignment V4 |