| From: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | 'Tom Lane' <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alexander Lakhin <exclusion(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "Aya Iwata (Fujitsu)" <iwata(dot)aya(at)fujitsu(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE |
| Date: | 2026-04-02 03:20:59 |
| Message-ID: | OS9PR01MB12149DEAB9D2FAF32C1E8079DF551A@OS9PR01MB12149.jpnprd01.prod.outlook.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear hackers,
Thanks for paying attention the thread.
I've been considering why the XLogFileClose() is slow only on widowbird but I
have no idea. But on this thread, I think we can just put a workaround for
stabilization.
> I don't think I want to propose a GUC for this, but could it make
> sense to check for an environment variable, similarly to PGCTLTIMEOUT
> and PG_TEST_TIMEOUT_DEFAULT? Whichever way we do it, it could replace
> the existing crude hack to change the max wait in injection-point
> mode.
I feel it might be a better approach, attached one implemented the idea.
I did not use the term "_TEST_" because such env variables are only referred
in test modules or binaries. But I did not update the documentation.
Best regards,
Hayato Kuroda
FUJITSU LIMITED
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Introduce-PG_BACKEND_WAIT_MAX_RETRIES.patch | application/octet-stream | 5.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2026-04-02 03:31:37 | Re: LLVM 22 |
| Previous Message | Thomas Munro | 2026-04-02 03:20:41 | Re: LLVM 22 |