Tom Lane wrote:
> Martijn van Oosterhout <kleptog@svana.org> writes:
>> On Thu, Feb 09, 2006 at 09:33:35AM -0500, Tom Lane wrote:
>>> You'd have to go over a lot of code with a fine-tooth comb before
>>> putting this ability into the hands of ordinary users, else you'd be
>>> creating loopholes for DOS attacks (or worse).
>
>> Would it be reasonable to set this up so you can only create a shell
>> type within an explicit transaction and that you are required to define
>> the type completely before commit.
>
> I don't see any very easy way to enforce that, and it would break
> existing datatype-definition scripts if we did.
>
What do you think of my earlier suggestion. Skip all the 'create function' statements and
just add the "AS 'filename' LANGUAGE C" to the CREATE TYPE. It could be implemented while
maintaining backward compatibility I think?
Regards,
Thomas Hallgren
