On Sun, 2010-02-07 at 17:52 -0500, Tom Lane wrote:
> 
> > It would be useful to mention that the return value is volatile and
> can change across transactions or even within a transaction, just like
> ctid.
> 
> Hm.  I thought it was more reasonable to treat it as "stable", which
> is the normal case.  You're right that there are some corner cases
> where it could change without the caller's snapshot changing, but I'm
> not sure it's worth worrying about.

OK, even if its stable I think we need to mention it because it's not
obvious that the file we keep catalog data in could change name. It's a
also a change from earlier releases where that would never happen.

-- 
 Simon Riggs           www.2ndQuadrant.com

In response to

• Re: pgsql: Create a "relation mapping" infrastructure to support changing at 2010-02-07 22:52:02 from Tom Lane

pgsql-hackers by date

Next:	From: Andrew McNamara	Date: 2010-02-07 23:53:26
	Subject: Re: Confusion over Python drivers
Previous:	From: Tom Lane	Date: 2010-02-07 22:52:02
	Subject: Re: pgsql: Create a "relation mapping" infrastructure to support changing

pgsql-committers by date

Next:	From: User Itagaki	Date: 2010-02-08 03:33:39
	Subject: pgstatsinfo - pg_statsinfo: New Directory
Previous:	From: Tom Lane	Date: 2010-02-07 22:52:02
	Subject: Re: pgsql: Create a "relation mapping" infrastructure to support changing