From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
Cc: | Markur Sens <markursens(at)gmail(dot)com>, pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Additional accessors via the Extension API ? |
Date: | 2022-02-20 16:34:45 |
Message-ID: | 279463.1645374885@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Julien Rouhaud <rjuju123(at)gmail(dot)com> writes:
> On Sun, Feb 20, 2022 at 12:31:22PM +0200, Markur Sens wrote:
>> Is this documented & expected behavior or it’s just happens to work?
> I don't think it's documented but it's an expected behavior, see
> https://github.com/postgres/postgres/blob/master/src/backend/parser/parse_func.c#L57-L88
It is documented, near the bottom of this section:
https://www.postgresql.org/docs/current/rowtypes.html#ROWTYPES-USAGE
Other relevant oddities are mentioned in
https://www.postgresql.org/docs/current/xfunc-sql.html#XFUNC-SQL-COMPOSITE-FUNCTIONS
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-02-20 19:02:42 | Re: Strange results when casting string to double |
Previous Message | Carsten Klein | 2022-02-20 16:00:45 | Re: Strange results when casting string to double |