From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Cornelia Boenigk" <poppcorn(at)cornelia-boenigk(dot)de> |
Cc: | "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Qestion about CREATE FUNCTION |
Date: | 2002-03-01 21:41:32 |
Message-ID: | 1646.1015018892@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Cornelia Boenigk" <poppcorn(at)cornelia-boenigk(dot)de> writes:
> Could anybody explain this behaviour?
See
http://www.ca.postgresql.org/users-lounge/docs/7.2/postgres/xfunc-sql.html
which says in part:
In the present release of PostgreSQL there are some unpleasant
restrictions on how functions returning composite types can be
used. Briefly, when calling a function that returns a row, we cannot
retrieve the entire row. We must either project a single attribute out
of the row or pass the entire row into another function. (Trying to
display the entire row value will yield a meaningless number.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Francisco Reyes | 2002-03-01 21:48:16 | Shared buffers vs large files |
Previous Message | Jean-Luc Lachance | 2002-03-01 21:33:42 | Re: improving performance of UNION and ORDER BY |