Message-ID: <65eb4d7a46a2759dc2583f274bf50d16811caebe.camel@cybertec.at>
Subject: Re: BUG #18793: PLpgSQL Function Returning Type of Table is not
 match for varchar(n) data type via Return Query
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: ugurlu2001@hotmail.com, pgsql-bugs@lists.postgresql.org
Date: Tue, 04 Feb 2025 16:13:46 +0100
In-Reply-To: <18793-07a72289887f0966@postgresql.org>
References: <18793-07a72289887f0966@postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.54.3 (3.54.3-1.fc41) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/65eb4d7a46a2759dc2583f274bf50d16811caebe.camel%40cybertec.at>
Precedence: bulk

On Tue, 2025-02-04 at 12:43 +0000, PG Bug reporting form wrote:
> I have a set of "Functions" that I created dynamically with PLPgSQL and a=
re
> connected to each other in a chain.
>=20
> The first function dynamically creates the second function. The second
> function returns a set of values with a dynamic "Return Query" statement =
and
> a reference to "Returns Table (field1 type1, field2 type2 .... )".
>=20
> Basically, the result set seems to return exactly the desired result. The
> exception is the varchar(n) fixed-length data type. Although the result s=
et
> is expected to be varchar(n) -a fixed-length value is expected-, a result=
 of
> type character varying (length indeterminate) is obtained.
>=20
> [...]
>=20
> As far as I have determined, the Postgresql database engine somehow retur=
ns
> the varchar(n) - Fixed Length - data type as a "character varying" -
> indefinite length data type.
>=20
> I hope this situation, which I observed as a problem, will be fixed as so=
on
> as possible.

That is working asdesigned.  Why is it a problem for you?

Yours,
Laurenz Albe