Re: pg_tablespace.spclocation column removed in 9.2

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Pavel Golub <pavel(at)gf(dot)microolap(dot)com>, Pavel Golub <pavel(at)microolap(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_tablespace.spclocation column removed in 9.2
Date: 2012-06-25 13:46:26
Message-ID: 20031.1340631986@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Pavel Golub <pavel(at)microolap(dot)com> writes:
> I'm aware of problems caused by this hard coded column. My proposal is
> to convert pg_tablespace to system view may be?

It's not that easy to make a 100% backwards compatible view for a system
catalog. The main sticking point is the OID column; see recent problems
with pg_roles' OID column for an example. On the whole I don't think
renaming pg_tablespace and inserting a mostly-compatible view would be
a net advance.

More generally, I don't see that this particular incompatibility in
the system catalogs is worse than many others that we've perpetrated.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2012-06-25 14:08:31 Re: pg_tablespace.spclocation column removed in 9.2
Previous Message Pavel Golub 2012-06-25 08:10:23 Re: pg_tablespace.spclocation column removed in 9.2

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2012-06-25 14:08:31 Re: pg_tablespace.spclocation column removed in 9.2
Previous Message Andres Freund 2012-06-25 13:43:39 Re: Catalog/Metadata consistency during changeset extraction from wal