Message-ID: <51C2FAE6.6000104@gmx.net>
Date: Thu, 20 Jun 2013 08:51:50 -0400
From: Peter Eisentraut <peter_e@gmx.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8;
 rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: Craig Ringer <craig@2ndquadrant.com>
CC: cedric@2ndquadrant.com, pgsql-hackers@postgresql.org,
 Andrew Dunstan <andrew@dunslane.net>
Subject: Re: Bugfix and new feature for PGXS
References: <201306181552.36673.cedric@2ndquadrant.com>
 <201306191832.25310.cedric@2ndquadrant.com> <51C1E0D5.5070008@dunslane.net>
 <201306192058.23832.cedric@2ndquadrant.com>
 <1371698781.13762.48.camel@vanquo.pezone.net>
 <51C29153.60708@2ndquadrant.com>
In-Reply-To: <51C29153.60708@2ndquadrant.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

On 6/20/13 1:21 AM, Craig Ringer wrote:
> As you note, the other option is to just refer to extension headers by
> their unqualified name. I'm *really* not a fan of that idea due to the
> obvious clash possibilities with Pg's own headers or system headers,
> especially given that the whole idea of extensions is that they're user
> supplied. Not having any kind of namespacing is worrying.

We already install all PostgreSQL server header files into a separate
directory, so the only clashes you have to worry about are with other
extensions and with the backend.  And you have to do that anyway,
because you will have namespace issues for the shared libraries, the
symbols in those libraries, and the extension names.


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers