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. ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
