Re: CREATE AGGREGATE disallows STYPE = internal

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

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?

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.

...Robert

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-11-14 16:25:39 Re: Sometimes pg_dump generates dump which is not restorable
Previous Message Andrew Dunstan 2008-11-14 16:20:07 Re: gram.y => preproc.y