From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | Jan Wieck <wieck(at)debis(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] update_pg_pwd |
Date: | 1999-12-13 15:46:04 |
Message-ID: | 11707.945099964@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I wrote:
> The thing I'm unhappy about is that "0" is being overloaded way too far
> as a function argument/result type in pg_proc. Currently it could mean:
> * unused position in proargtype array;
> * erroneous definition;
> * "C string" parameter to a type input function (but, for who
> knows what reason, C string outputs from type-output functions
> are represented differently);
> * user proc returning some kind of tuple;
> * user proc returning nothing in particular;
> and who knows what else.
Almost forgot:
* function accepting any data type whatever
(I think COUNT() is the only one at present).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-12-13 16:02:41 | Re: [HACKERS] update_pg_pwd |
Previous Message | Tom Lane | 1999-12-13 15:44:09 | Re: [HACKERS] update_pg_pwd |