Re: pgsql: Create a "relation mapping" infrastructure to support changing - Mailing list pgsql-committers

From Simon Riggs
Subject Re: pgsql: Create a "relation mapping" infrastructure to support changing
Date
Msg-id 1265584001.27207.237.camel@ebony
Whole thread Raw
In response to Re: pgsql: Create a "relation mapping" infrastructure to support changing  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-committers
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


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pgsql: Create a "relation mapping" infrastructure to support changing
Next
From: itagaki@pgfoundry.org (User Itagaki)
Date:
Subject: pgstatsinfo - pg_statsinfo: New Directory