Re: pg_stat_reset round 3 - Mailing list pgsql-patches

From Alvaro Herrera
Subject Re: pg_stat_reset round 3
Date
Msg-id Pine.LNX.4.44.0208060212020.5523-100000@cm-lcon1-46-187.cm.vtr.net
Whole thread Raw
In response to Re: pg_stat_reset round 3  ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>)
List pgsql-patches
Christopher Kings-Lynne dijo:

> > Interesting that all callable function must return a type.  I did:
> >
> >     test=> select proname from pg_proc where prorettype = 0;
> >
> > and none of the functions with 0 prorettype can be called from psql.  I
> > guess boolean is the best we can do.  I guess because it is a function
> > it has to return something.
>
> Yeah, because otherwise what does the SELECT return?  It has to return at
> least one column?  It would be odd to just go SELECT blah() and have the
> prompt just come back to you.  However, it would be nice to be able to go
> "CALL blah()" and have it return nothing except maybe a 'CALL' string.

What's so bad about returning a SQL NULL in SELECT ?  Seems an arbitrary
limitation to me.

--
Alvaro Herrera (<alvherre[a]atentus.com>)
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)


pgsql-patches by date:

Previous
From: "Christopher Kings-Lynne"
Date:
Subject: Re: pg_stat_reset round 3
Next
From: Bruce Momjian
Date:
Subject: Re: clean up assertion code