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

From Robert Haas
Subject Re: Closing some 8.4 open items
Date
Msg-id 603c8f070904110858w180d4b9fk30fc0f9bc40fcfe3@mail.gmail.com
Whole thread Raw
In response to Re: Closing some 8.4 open items  (David Fetter <david@fetter.org>)
List pgsql-hackers
On Sat, Apr 11, 2009 at 8:58 AM, David Fetter <david@fetter.org> wrote:
> On Sat, Apr 11, 2009 at 08:52:31AM -0400, Robert Haas wrote:
>> On Sat, Apr 11, 2009 at 5:06 AM, Grzegorz Jaskiewicz
>> <gj@pointblue.com.pl> wrote:
>> > On 11 Apr 2009, at 08:01, Hitoshi Harada wrote:
>> >> 2009/4/11 David Fetter <david@fetter.org>:
>> >>> On Sat, Apr 11, 2009 at 03:48:33PM +0900, Hitoshi Harada wrote:
>> >>>> Yeah, but all the window functions are stored in pg_proc.
>> >>> So are aggregate functions, and they have their own separate way of
>> >>> being addressed in psql :)
>> >> Aggregate functions are stored in pg_aggregate. And they are
>> >> combinations of plain function which is stored in pg_proc.
>> > Maybe trigger functions should be displayed separately too than ?
>>
>> We're up to at least four different categories of functions that
>> people think might require special treatment: window, trigger, I/O,
>> everything else.
>
> The current psql has \da and \df, the latter of which now includes I/O
> functions.  I contend that windowing functions are different enough
> that they require a separate category.
>
> You do bring up an interesting point for 8.5 or later, which would be
> a complete redo of psql from the ground up.  Let's hash out a proposal
> for that in a separate thread once we get 8.4 out the door :)

:-)

I'm sure consensus will be reached quickly and painlessly.  :-)

...Robert


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Closing some 8.4 open items
Next
From: Pavel Stehule
Date:
Subject: Patch for 8.5, transformationHook