Re: Bug in CREATE FUNCTION with character type (CONFIRMED BUG)

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Kevin J Bluck <technology(at)netce(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Bug in CREATE FUNCTION with character type (CONFIRMED BUG)
Date: 2010-06-01 04:44:49
Message-ID: AANLkTinycHZYdA9oK3SOgCJ9ERy7rZbrheq0IRThK2Ux@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2010/5/31 Bruce Momjian <bruce(at)momjian(dot)us>:
> Pavel Stehule wrote:
>> 2010/4/15 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> > Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
>> >> I think, so RETURNS TABLE can be modified for returning typmode
>> >> without significant problems - this function is called in table
>> >> context and I don't see any problematic use case.
>> >
>> > RETURNS TABLE is just a shorthand for some OUT parameters. ?I don't
>> > believe it's either easy or a good idea to make it work differently
>> > from every other function-argument-or-result case.
>> >
>>
>> I don't know now. It minimally have to be documented
>
> Can you suggest some documentation?

some like "typmod in declared parameters are ignored - so returned
table can not be same as table declared by CREATE STATEMENT."

Pavel

>
> --
>  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
>  EnterpriseDB                             http://enterprisedb.com
>
>  + None of us is going to be here forever. +
>
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Heikki Linnakangas 2010-06-01 09:00:23 Re: BUG #5487: dblink failed with 63 bytes connection names
Previous Message Takahiro Itagaki 2010-06-01 02:55:11 Re: BUG #5487: dblink failed with 63 bytes connection names