Re: Shared catalogs vs pg_global tablespace

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Shared catalogs vs pg_global tablespace
Date: 2010-02-04 17:32:43
Message-ID: 603c8f071002040932y73a06e7bu7b21ac2084192e1d@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Feb 4, 2010 at 10:30 AM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
> Tom Lane wrote:
>> I'm not sure whether allowing that would be good or bad.  I see no
>> obvious killer reason why it'd be bad, but it seems like the kind of
>> thing we might regret someday.  pg_global is in some sense an
>> implementation artifact, so allowing users to depend on it might be
>> bad in the long run.
>
> Agreed, it feels scary to allow it.

+1.

...Robert

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-02-04 17:34:33 Re: Largeobject Access Controls (r2460)
Previous Message Andrew Dunstan 2010-02-04 17:28:30 Re: PG 9.0 and standard_conforming_strings