Re: cleanup patches for incremental backup - Mailing list pgsql-hackers

From Nathan Bossart
Subject Re: cleanup patches for incremental backup
Date
Msg-id 20240124193922.GA2711912@nathanxps13
Whole thread Raw
In response to Re: cleanup patches for incremental backup  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: cleanup patches for incremental backup
List pgsql-hackers
On Wed, Jan 24, 2024 at 02:08:08PM -0500, Robert Haas wrote:
> On Wed, Jan 24, 2024 at 1:05 PM Nathan Bossart <nathandbossart@gmail.com> wrote:
>> Otherwise, I think we'll probably need to add some additional logging to
>> figure out what is happening...
> 
> Where, though? I suppose we could:
> 
> 1. Change the server code so that it logs each WAL summary file
> removed at a log level high enough to show up in the test logs.
> 
> 2. Change the TAP test so that it prints out readdir(WAL summary
> directory) at various points in the test.

That seems like a reasonable starting point.  Even if it doesn't help
determine the root cause, it should at least help rule out concurrent
summary removal.

-- 
Nathan Bossart
Amazon Web Services: https://aws.amazon.com



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: dblink query interruptibility
Next
From: Nathan Bossart
Date:
Subject: Re: Remove redundant HandleWalWriterInterrupts()