Re: CREATE AGGREGATE disallows STYPE = internal

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Robert Haas" <robertmhaas(at)gmail(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: CREATE AGGREGATE disallows STYPE = internal
Date: 2008-11-14 16:38:00
Message-ID: 28118.1226680680@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Robert Haas" <robertmhaas(at)gmail(dot)com> writes:
> On Fri, Nov 14, 2008 at 10:12 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "Robert Haas" <robertmhaas(at)gmail(dot)com> writes:
>>> I would feel a lot better about it if we could invent some way of
>>> distinguishing between different types of "internal", based on what is
>>> actually being pointed to.
>>
>> Yeah, we discussed that awhile ago, but nothing's been done about it.
>> At this point I doubt it will happen for 8.4.

> That's a shame. Do you happen to have a pointer to the relevant
> discussions in the archives?

http://archives.postgresql.org/pgsql-hackers/2008-08/msg00644.php

> Without that, it seems that the change you're proposing is totally
> unsafe. It's not just a question of malicious activity: a clueless
> admin (a category we've all been in from time to time...) could
> relatively easily create a configuration that crashes the backend.

It's no more dangerous than allowing the admin to create functions
taking or returning internal to begin with. Basically, if you are
superuser, there are no training wheels.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-14 16:43:15 Re: Simple postgresql.conf wizard
Previous Message Michael Meskes 2008-11-14 16:37:49 Re: gram.y => preproc.y