Re: Assertion failure during initdb with transaction_timeout set

Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> writes:
> While discussing the assertion failure with track_commit_timestamp=on during initdb [1],
> I found a similar issue with another GUC: transaction_timeout.

> This happens because enable_timeout() tries to start the transaction timeout
> before InitializeTimeouts() has been called, i.e., the timeout subsystem
> hasn't been initialized yet.

> To address this, I'm thinking forcibly setting transaction_timeout to 0
> during bootstrap or in initdb.

I don't like inventing a different workaround for each case we find.
The precedent established by the other patch is to prevent the
relevant subsystem from starting if IsBootstrapProcessingMode().
Can't we do something similar here?

regards, tom lane