| From: | 姜梦洋 <minesunny(at)icloud(dot)com> |
|---|---|
| To: | 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 08:11:26 |
| Message-ID: | 33B6EA55-67C0-48DA-B87D-6DE1A0CD9377@icloud.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
sorry for images，here are clear；

> On Sep 13, 2023, at 3:24 PM, 姜梦洋 <minesunny(at)icloud(dot)com> wrote:
>
> 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.). now I run the code and get some results；
> <1.jpeg><2.jpeg><3.jpeg><4.jpeg><5.jpeg>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2023-09-13 10:42:45 | Re: [16] ALTER SUBSCRIPTION ... SET (run_as_owner = ...) is a no-op |
| Previous Message | 姜梦洋 | 2023-09-13 07:24:14 | the same time value return different values，is it a problem |