Re: Apparent bug in WAL summarizer process (hung state) - Mailing list pgsql-hackers

From Israel Barth Rubio
Subject Re: Apparent bug in WAL summarizer process (hung state)
Date
Msg-id CAO_rXXC7x5VrYeqdqNWALPAoLRyHMbqtGYzThr23N=KSBEj2CQ@mail.gmail.com
Whole thread Raw
In response to Re: Apparent bug in WAL summarizer process (hung state)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
> Yeah, this is a bug. It seems that the WAL summarizer process, when
> restarted, wants to restart from wherever it was previously
> summarizing WAL, which is correct if that WAL is still around, but if
> summarize_wal has been turned off in the meanwhile, it might not be
> correct. Here's a patch to fix that.

Thanks for checking this!

> Thanks. New version attached.

And besides that, thanks for the patch, of course!

I compiled Postgres locally with your patch. I attempted to break it several
times, both manually and through a shell script.

No success on that -- which in this case is actually success :)
The WAL summarizer seems able to always resume from a valid point,
so `pg_basebackup` isn't failing anymore.

pgsql-hackers by date:

Previous
From: Marcos Pegoraro
Date:
Subject: Is missing LOGIN Event on Trigger Firing Matrix ?
Next
From: Andrew Dunstan
Date:
Subject: Re: Is missing LOGIN Event on Trigger Firing Matrix ?