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

From: "Kevin J Bluck" <kevin(dot)bluck(at)netce(dot)com>
To: "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-04-14 15:27:22
Message-ID: 7b8eba69d1c4c545a3fa03a5bc0b4b40@netce.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> I'd certainly call this a bug, if not a couple of different bugs.

There seems to be more. I see a problem not just with unqualified char not being treated equivalent to char(1). I also see a general problem with RETURNS TABLE disregarding any explicit lengths declared for any character type. For example, if you declare a RETURNS TABLE column as VARCHAR(15), it seems to actually consider it as if you had declared it unqualified VARCHAR, equivalent to TEXT. Similarly, a column defined as CHAR(2) will also be treated as unqualified CHAR without an explicit length, with the further problem reported by Pavel of being treated as unlimited length instead of equivalent to CHAR(1) as expected. In other words, it seems to be effectively impossible to declare explicit lengths for RETURNS TABLE character type columns.

This doesn't happen with the RETURNS SETOF variation, only RETURNS TABLE.

Regards,

--- Kevin

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2010-04-14 15:32:16 Re: BUG #5412: test case produced, possible race condition.
Previous Message Tom Lane 2010-04-14 14:49:36 Re: BUG #5412: test case produced, possible race condition.