| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Vladlen Popolitov <v(dot)popolitov(at)postgrespro(dot)ru> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Avoiding roundoff error in pg_sleep() |
| Date: | 2025-09-26 15:08:10 |
| Message-ID: | CAKFQuwa9mmwqt5JnLH8Fzq=Hb4cxAFX+M7BJwCGBS-_AZ8LkyA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Friday, September 26, 2025, Vladlen Popolitov <v(dot)popolitov(at)postgrespro(dot)ru>
wrote:
>
> It looks like sleep has the wrong place in a function. It should be
> an utility command, that does not start a transaction.
>
Then write that command. We’re not going to change pg_sleep. It’s works
just as advertised. True, it probably should never be used in production.
I can see a pipeline sequence tossing a wait command into the flow so
having the server accept a wait instruction has at least some immediate
merit.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-09-26 15:10:19 | Re: Avoiding roundoff error in pg_sleep() |
| Previous Message | Álvaro Herrera | 2025-09-26 15:02:05 | Re: Remove unused for_all_tables field from AlterPublicationStmt |