| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 姜梦洋 <minesunny(at)icloud(dot)com> |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: the same time value return different values，is it a problem |
| Date: | 2023-09-13 14:17:28 |
| Message-ID: | 2961695.1694614648@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?utf-8?B?5aec5qKm5rSL?= <minesunny(at)icloud(dot)com> writes:
> I find the time type accuracy of the database. Using PreparedStatement, the accuracy found out for the sixth time is different from the first five times. This number is exactly the same as the threshold of the PreparedStatement. I can understand that the database can optimize PreparedStatements and reduce repeated parsing and other unnecessary operations. but I don’t quite understand how such processing will affect the execution results(Or maybe I don’t have a deep understanding of PreparedStatement.).
If you're using JDBC, this is probably the same effect discussed at
It's got something to do with retrieving the query results in binary
mode instead of text. The query result at the server is the same,
but the JDBC driver is rendering it differently.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gokul Krishnan | 2023-09-13 17:06:29 | Re: BUG #18098: Console code page issue Postgresql 14.7 |
| Previous Message | Daniel Gustafsson | 2023-09-13 13:24:42 | Re: Memory leak on subquery as scalar operand |