Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC
| От | ZhangChi |
|---|---|
| Тема | Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC |
| Дата | |
| Msg-id | tencent_6A625E6BCFAF916999E0C64185022D99ED0A@qq.com обсуждение исходный текст |
| Ответ на | Re: BUG #19350: Short circuit optimization missed when running sql scriptes in JDBC ("David G. Johnston" <david.g.johnston@gmail.com>) |
| Ответы |
Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC
|
| Список | pgsql-bugs |
Hi David J.
Thanks for your reply. I wonder why this query triggers an error under JDBC but not in the CLI.
Original
From: David G. Johnston <david.g.johnston@gmail.com> Date: 2025-12-10 21:33 To: 798604270@qq.com <798604270@qq.com>, pgsql-bugs@lists.postgresql.org <pgsql-bugs@lists.postgresql.org> Subject: Re: BUG #19350: Short circuit optimization missed when running sqlscriptes in JDBC |
The following bug has been logged on the website:
Bug reference: 19350
Logged by: Chi Zhang
Email address: 798604270@qq.com
PostgreSQL version: 17.6
Operating system: ubuntu 24.04 with docker
Description:
Hi,
In the following test case, if I run it in JDBC, the prepared statement will
trigger a divide by zero error. But if run it in command line, there will
not be the same error.
This isn’t a bug in PostgreSQL, it’s a bug in the query you’ve written. The expectation of short-circuiting is flawed - the non-failure outcome is not something than can be relied upon.
David J.
В списке pgsql-bugs по дате отправления: