Skip site navigation (1) Skip section navigation (2)

Re: pgsql: Create a "relation mapping" infrastructure to support changing

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Create a "relation mapping" infrastructure to support changing
Date: 2010-02-07 23:06:41
Message-ID: 1265584001.27207.237.camel@ebony (view raw or flat)
Thread:
Lists: pgsql-committerspgsql-hackers
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

pgsql-hackers by date

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

pgsql-committers by date

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

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group