Re: pg_execute_from_file review

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "David E(dot) Wheeler" <david(at)kineticode(dot)com>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Itagaki Takahiro <itagaki(dot)takahiro(at)gmail(dot)com>, Joshua Tolley <eggyknap(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_execute_from_file review
Date: 2010-12-07 16:23:43
Message-ID: 4CFE5F8F.7020708@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/07/2010 11:13 AM, Robert Haas wrote:
> On Mon, Dec 6, 2010 at 2:36 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> There's a difference between whether an extension as such is considered
>> to belong to a schema and whether its contained objects do. We can't
>> really avoid the fact that functions, operators, etc must be assigned to
>> some particular schema. It seems not particularly important that
>> extension names be schema-qualified, though --- the use-case for having
>> two different extensions named "foo" installed simultaneously seems
>> pretty darn small. On the other hand, if we were enforcing that all
>> objects contained in an extension belong to the same schema, it'd make
>> logistical sense to consider that the extension itself belongs to that
>> schema as well. But last I heard we didn't want to enforce such a
>> restriction.
> Why not? This feature seems to be pretty heavily designed around the
> assumption that everything's going to live in one schema, so is there
> any harm in making that explicit?
>

In previous discussions IIRC the consensus was that we should not force
that on either Extension writers or users.

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2010-12-07 16:24:14 Final(?) proposal for wal_sync_method changes
Previous Message Kevin Grittner 2010-12-07 16:14:24 Re: serializable read only deferrable