RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE
Date
Msg-id OS9PR01MB12149DEAB9D2FAF32C1E8079DF551A@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: [PROPOSAL] Termination of Background Workers for ALTER/DROP DATABASE
List 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

pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: LLVM 22
Next
From: Tom Lane
Date:
Subject: Re: LLVM 22