Alvaro Herrera <[email protected]> wrote: > On 2026-Jan-05, Antonin Houska wrote: > > > Mihail Nikalayeu <[email protected]> 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_rgajvtu...@mail.gmail.com
Thanks for the hint! It seems that the already committed WaitForLSN() function does what I need. -- Antonin Houska Web: https://www.cybertec-postgresql.com
