From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | Israel Barth Rubio <barthisrael(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Apparent bug in WAL summarizer process (hung state) |
Date: | 2024-06-24 23:01:12 |
Message-ID: | Znn6uC_DRYcGwfTp@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Jun 24, 2024 at 02:56:00PM -0300, Israel Barth Rubio wrote:
> I've been playing a bit with the incremental backup feature which might
> come as
> part of the 17 release, and I think I hit a possible bug in the WAL
> summarizer
> process.
Thanks for testing new features and for this report!
> FWIW, once I restart Postgres the WAL summarizer process gets back to normal
> functioning. It seems to me there is some race condition between when a WAL
> file
> is removed and when `summarize_wal` is re-enabled, causing the process to
> keep
> looking for a WAL file that is the past.
I am adding an open item to track this issue, to make sure that this
is looked at.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Joel Jacobson | 2024-06-24 23:21:14 | Re: Add pg_get_acl() function get the ACL for a database object |
Previous Message | David G. Johnston | 2024-06-24 22:53:46 | Re: improve predefined roles documentation |