| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: cleanup patches for incremental backup |
| Date: | 2024-01-24 19:39:22 |
| Message-ID: | 20240124193922.GA2711912@nathanxps13 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2024-01-24 19:40:19 | Re: Remove redundant HandleWalWriterInterrupts() |
| Previous Message | Fujii Masao | 2024-01-24 19:23:39 | Re: dblink query interruptibility |