BUG #18780: Bindings types are lost for complex queries

From: PG Bug reporting form <noreply(at)postgresql(dot)org>
To: pgsql-bugs(at)lists(dot)postgresql(dot)org
Cc: vik(at)notexi(dot)st
Subject: BUG #18780: Bindings types are lost for complex queries
Date: 2025-01-19 22:25:42
Message-ID: 18780-bae540b8dbfe4cdc@postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 18780
Logged by: Viktr
Email address: vik(at)notexi(dot)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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message PG Bug reporting form 2025-01-20 12:52:38 BUG #18781: pg group gy The number of returned data bars in a field is inconsistent
Previous Message Jeff Janes 2025-01-19 02:32:02 Re: BUG #18779: Segmentation fault while trying to connect via psql