BUG #18780: Bindings types are lost for complex queries - Mailing list pgsql-bugs

From PG Bug reporting form
Subject BUG #18780: Bindings types are lost for complex queries
Date
Msg-id 18780-bae540b8dbfe4cdc@postgresql.org
Whole thread Raw
Responses Re: BUG #18780: Bindings types are lost for complex queries
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      18780
Logged by:          Viktr
Email address:      vik@notexi.st
PostgreSQL version: 17.2
Operating system:   Linux d2c635331de7 6.10.14-linuxkit #1 SMP PREEMPT
Description:

Hi there,

Actual discussion is here: https://github.com/pgjdbc/pgjdbc/issues/3482
In brief: I do understand that "select 1 as one, 2 as two, 3 as three" might
have lack of type info. But I suppose, in case these values are used in the
assignment, the type could be taken from the corresponding column type. Like
for "insert into sometable(one, two, three) select 1 as one, 2 as two, 3 as
three" it is obvious that types should match.


pgsql-bugs by date:

Previous
From: Jeff Janes
Date:
Subject: Re: BUG #18779: Segmentation fault while trying to connect via psql
Next
From: PG Bug reporting form
Date:
Subject: BUG #18781: pg group gy The number of returned data bars in a field is inconsistent