From: Tom Lane <tgl@sss.pgh.pa.us>
To: spsamaan@gmail.com
cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18777: Error running unnest function in a two phase commit
 transaction
In-reply-to: <18777-3fa8180f86edfb55@postgresql.org>
References: <18777-3fa8180f86edfb55@postgresql.org>
Comments: In-reply-to PG Bug reporting form <noreply@postgresql.org>
	message dated "Thu, 16 Jan 2025 18:35:54 +0000"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1850520.1737055558.1@sss.pgh.pa.us>
Date: Thu, 16 Jan 2025 14:25:58 -0500
Message-ID: <1850521.1737055558@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1850521.1737055558%40sss.pgh.pa.us>
Precedence: bulk

PG Bug reporting form <noreply@postgresql.org> writes:
> I have a query " SELECT * FROM UNNEST(ARRAY[123456]) " running in a Groovy 4
> code. That code is running in a weblogic 14 server. The driver I'm using is
> postgresql-42.7.3.jar.
> When the weblogic datasource is configured as a Two-phase commit I got an
> error: 
> Caused by: org.postgresql.util.PSQLException: ERROR: function
> unnest(unknown) is not unique

Presumably what is happening is that the query actually being sent
to the server is something like

	SELECT * FROM UNNEST($1)

with no hint as to what the data type of $1 is, making it impossible
to infer the unnest's result type.  I don't know whether the JDBC
driver or weblogic is more at fault, but this isn't a server-side bug.
Some level on the client side has to take responsibility for
specifying the data type of the parameter.

			regards, tom lane