| From: | Hannu Krosing <hannuk(at)google(dot)com> |
|---|---|
| To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | nagata(at)sraoss(dot)co(dot)jp, coelho(at)cri(dot)ensmp(dot)fr, gregsmithpgsql(at)gmail(dot)com, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, david(dot)christensen(at)crunchydata(dot)com |
| Subject: | Re: pgbench logging broken by time logic changes |
| Date: | 2021-07-08 14:46:51 |
| Message-ID: | CAMT0RQReCH-VO6fko4i9=iZLT9qNL5YUnX0Zbt_d-_V9zUCyCg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 17, 2021 at 7:18 AM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
>
> I'm not sure we have transaction lasts for very short time that
> nanoseconds matters.
>
Nanoseconds may not matter yet, but they could be handy when for
example we want to determine the order of parallel query executions.
We are less than an order of magnitude away from being able to do 1M
inserts/updates/deletes per second, so microseconds already are not
always 100% reliable.
We could possibly move to using LSNs fetched as part of the queries
for this case, but this will surely introduce more problems than it
solves :)
Cheers
-----
Hannu Krosing
Google Cloud - We have a long list of planned contributions and we are hiring.
Contact me if interested.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-07-08 14:57:22 | Re: pgsql: Don't try to print data type names in slot_store_error_callback( |
| Previous Message | gkokolatos | 2021-07-08 14:18:40 | Re: Teach pg_receivewal to use lz4 compression |