Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Dave Cramer <davecramer(at)postgres(dot)rocks>
Cc: ZhangChi <798604270(at)qq(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC
Date: 2025-12-17 14:51:08
Message-ID: CAKAnmm+G4pjdfKpXzrxVWv4s62_RcpAR4fO8++nYxjRGCqbDOw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

>
> Possibly because JDBC does everything using the V3 protocol whereas psql
> does not. psql uses simple query.

Maybe JDBC is doing something else? I cannot duplicate the error when doing
it via the protocol (DBD::Pg) or via psql. Even forcing non-server-side
prepares (i.e. making the driver replace the vars itself) fails to fail.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Greg Sabino Mullane 2025-12-17 14:54:08 Re: BUG #19357: PostgreSQL generates a custom plan that performs worse than the generic plan for a certain query.
Previous Message Dave Cramer 2025-12-17 12:55:25 Re: BUG #19350: Short circuit optimization missed when runningsqlscriptes in JDBC