Re: Closing some 8.4 open items - Mailing list pgsql-hackers

From Hitoshi Harada
Subject Re: Closing some 8.4 open items
Date
Msg-id e08cc0400904110627q2707d9fbxa9b2afb2ab6ff43a@mail.gmail.com
Whole thread Raw
In response to Re: Closing some 8.4 open items  (Grzegorz Jaskiewicz <gj@pointblue.com.pl>)
List pgsql-hackers
2009/4/11 Grzegorz Jaskiewicz <gj@pointblue.com.pl>:
>
> On 11 Apr 2009, at 13:33, Hitoshi Harada wrote:
>
>>> Maybe trigger functions should be displayed separately too than ?
>>
>> You don't catch the point. The aggregate entries in pg_proc have
>> prosrc = 'aggregate_dummy', which means they're dummy and the entities
>> are stored in pg_aggregate. Triggers in pg_proc are dummy? No, they
>> are actually plain functions with trigger return type.
>
> yes, that's from strictly insider's point of view. Based on the
> implementation of that in postgresql, but you guys talk about user
> perspective, after all - psql is for users, not only for postgresql hackers.
> So the better question would be, can you use window, aggregate, trigger
> functions the same way other procedures ? I guess the answer is no :)
> Hence, if classify - than I would suggest to do it completely and fair, and
> not judge it only from postgresql-hacker perspective.
>
> I am hardly the postgresql-hacker myself, so it is my opinion from user
> perspective, that also understands where your opinion comes from.
>

It seems I that didn't catch the point. Still, I don't like such
variable syntax for psql -- window, aggregate, plain function,
trigger, i/o, cast and more -- I cannot remeber them all :(

Regards,


-- 
Hitoshi Harada


pgsql-hackers by date:

Previous
From: David Fetter
Date:
Subject: Re: Closing some 8.4 open items
Next
From: Tom Lane
Date:
Subject: Re: Allow COMMENT ON to accept an expression rather than just a string