| From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, Postgresql-Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Lazy xid assingment V2 |
| Date: | 2007-09-01 02:51:30 |
| Message-ID: | 20070901025130.GY8046@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> I note that pg_description defines xid_age as "age of a transaction ID,
> in transactions before current transaction", and I'm content to stick
> with that definition. Even if it does force consuming an XID. I'm not
> sure that we could devise a comparably succinct description of any of
> these other proposed behaviors, nor that we should even consider
> changing that description.
Hmm, what happens if somebody calls
select age(xmin) from bigtable
?
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | August Zajonc | 2007-09-01 04:30:12 | Re: [PATCH] Lazy xid assingment V2 |
| Previous Message | Florian G. Pflug | 2007-09-01 02:50:53 | Re: [PATCH] Lazy xid assingment V2 |