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
0001-Introduce-PG_BACKEND_WAIT_MAX_RETRIES.patch
Description: 0001-Introduce-PG_BACKEND_WAIT_MAX_RETRIES.patch
