| From: | "Imseih (AWS), Sami" <samimseih(at)gmail(dot)com> |
|---|---|
| To: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Bertrand Drouvot <bertranddrouvot(dot)pg(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Restart pg_usleep when interrupted |
| Date: | 2024-08-13 16:15:56 |
| Message-ID: | d76eff89-4c8d-4559-a4f4-96d04f67d8ee@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Please disregards this point from the last reply:
"""
2/ What if there are other callers in the future that wish
to instrument parallel vacuum workers? they will need to implement
similar logic.
"""
I misspoke about this and this point does not matter since only
vacuum sleep matters for this current discussion.
Regards,
Sami
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-08-13 16:40:27 | Re: Restart pg_usleep when interrupted |
| Previous Message | Imseih (AWS), Sami | 2024-08-13 16:07:46 | Re: Restart pg_usleep when interrupted |