Re: pg_class.relistemp

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <bruce(at)momjian(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_class.relistemp
Date: 2011-07-14 20:59:51
Message-ID: 4E1F58C7.4010305@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> There has never, ever, been a guarantee that the system catalogs don't
> change across versions. Anybody issuing such queries should expect to
> have to retest them and possibly change them in each new major release.

I know that's always been our policy. It his, however,
vendor-unfriendly because we don't supply any interface for many things
(such as temp tables) other than the system catalogs.

So if we're going to break compatibility, then we could stand to make a
little noise about it.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2011-07-14 21:06:33 Re: pg_class.relistemp
Previous Message Bruce Momjian 2011-07-14 20:59:24 Re: Need help understanding pg_locks