On 2026-Jan-05, Antonin Houska wrote:
> Mihail Nikalayeu <mihailnikalayeu@gmail.com> wrote:
> > Probably it is because
> > > 100000L, /* XXX Tune the delay. */
> >
> > 100 seconds is clearly too much.
>
> I confused milliseconds with microseconds. Since I was only running the code
> with debugger, the long delays didn't appear to be a problem.
>
> Instead of tuning the timeout, I'm thinking of introducing a condition
> variable that signals WAL flushing.
I think there is a patch that adds support for this in the queue already
-- see this message:
https://postgr.es/m/CAPpHfds-KiZRuCruc0jHxLSxLqzKcHJGwOFFA0b_RgaJvtUOEQ@mail.gmail.com
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"¿Qué importan los años? Lo que realmente importa es comprobar que
a fin de cuentas la mejor edad de la vida es estar vivo" (Mafalda)
