From: PG Bug reporting form <noreply@postgresql.org>
To: pgsql-bugs@lists.postgresql.org
Cc: drewk@cockroachlabs.com
Subject: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
Date: Tue, 14 May 2024 06:45:29 +0000
Message-ID: <18463-f8cd77e12564d8a2@postgresql.org> (raw)
The following bug has been logged on the website:
Bug reference: 18463
Logged by: Drew Kimball
Email address: drewk@cockroachlabs.com
PostgreSQL version: 16.3
Operating system: macOS
Description:
Hello,
I believe there may be a bug related to stored procedures with
polymorphic-typed OUT parameters:
CREATE PROCEDURE p(INOUT x ANYELEMENT) LANGUAGE SQL AS $$ SELECT x; $$;
CALL p(1);
The above example results in an error message "cannot display a value of
type anyelement", but I would expect it to succeed and output "1". This also
reproduces with the following stored procedures:
CREATE PROCEDURE p(INOUT x ANYELEMENT) LANGUAGE SQL AS $$ SELECT 1; $$;
CREATE PROCEDURE p(x ANYELEMENT, OUT y ANYELEMENT) LANGUAGE SQL AS $$ SELECT
x; $$;
CREATE PROCEDURE p(x ANYARRAY, OUT y ANYELEMENT) LANGUAGE SQL AS $$ SELECT
x[1]; $$;
Interestingly, this doesn't seem to reproduce when the OUT param has type
ANYARRAY. The following example succeeds:
CREATE PROCEDURE p(INOUT x ANYARRAY) LANGUAGE SQL AS $$ SELECT x; $$;
CALL p(ARRAY[1, 2, 3]);
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: noreply@postgresql.org, pgsql-bugs@lists.postgresql.org, drewk@cockroachlabs.com
Subject: Re: BUG #18463: Possible bug in stored procedures with polymorphic OUT parameters
In-Reply-To: <18463-f8cd77e12564d8a2@postgresql.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox