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. And then there are other categories you might want
to include/exclude: conversion functions, referential integrity
functions, operator functions, ... it quickly gets out of control.
Maybe we should consider some sort of option syntax for blackslash
commands. Like, \df -w to see just window functions, \df -c to see
just conversion functions, \df -wc to see those two types but not
anything else. Actually, I don't really like that syntax either,
because it's just propagating the existing dubious design decision of
identifying the behavior you want with longer and longer strings of
inscrutable single-digit modifiers. But some sort of more powerful
syntax would be good.
This problem is not limited to searching either - for example, I'd
like to be able to do "\d foo, except don't show me the foreign-keys
because there are a zillion of them and they make the output not fit
on the screen".
...Robert
