To: "Tom Lane" <tgl@sss.pgh.pa.us>
Cc: <pgsql-hackers@postgreSQL.org>
Subject: Re: Should creating a new base type require superuser status?
In-Reply-To: <23742.1217453388@sss.pgh.pa.us> (Tom Lane's message of "Wed\,
	30 Jul 2008 17\:29\:48 -0400")
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux)
References: <19715.1217447413@sss.pgh.pa.us>
	<87sktrgjdj.fsf@oxford.xeocode.com> <23742.1217453388@sss.pgh.pa.us>
From: Gregory Stark <stark@enterprisedb.com>
Organization: EnterpriseDB
Date: Wed, 30 Jul 2008 23:01:06 +0100
Message-ID: <87od4fghgd.fsf@oxford.xeocode.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


"Tom Lane" <tgl@sss.pgh.pa.us> writes:

>> As a consequence we could perhaps aim to make creating new types safe rather
>> than just deal with the fact that it's not safe currently? It would be nice if
>> non-superusers could create types which used an existing set of input/output
>> functions but defined new semantics.
>
> Unless you're going to allow them to create new C functions, I'm not
> clear on how much they're going to be able to change the semantics.

Well there's plenty that can be done just using text or bytea as
representations. citext, or uuid for example.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's RemoteDBA services!