| From: | "Aya Iwata (Fujitsu)" <iwata(dot)aya(at)fujitsu(dot)com> |
|---|---|
| To: | Xuneng Zhou <xunengzhou(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BGWORKER_INTERRUPTIBLE workers are never restarted after DROP/ALTER/CREATE DATABASE |
| Date: | 2026-11-10 10:32:45 |
| Message-ID: | OS9PR01MB12439C5F24B1007F9180B0403EA722@OS9PR01MB12439.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi
Thank you for the new version patch.
I have confirmed that the build succeeds and passes all regression tests on my machine.
```
* Terminates all background workers connected to the specified database. However,
- * If the worker is interruptible.
+ * If the worker is interruptible. A signal is sent directly to the worker.
*/
```
This is a minor point, sending a signal directly is to enable the bgworker restart setting, right?
I thought it would be helpful to clarify in the function description why a signal is sent directly.
For example, how about the following phrasing? Feel free to modify the wording as needed.
“A signal is sent directly to the worker so that it can be restarted according to the worker's bgw_restart_time setting.”
Regards,
Aya Iwata
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2026-11-10 10:33:54 | Re: Show 'Rows Removed by Filter' with two fractional digits in EXPLAIN |
| Previous Message | Ajin Cherian | 2026-11-10 10:27:43 | Re: Patch for migration of the pg_commit_ts directory |