| From: | Nick Ivanov <nick(dot)ivanov(at)enterprisedb(dot)com> |
|---|---|
| To: | Fabrice Chapuis <fabrice636861(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: incremental backup issue |
| Date: | 2026-07-13 16:26:00 |
| Message-ID: | CALP_NYR-Q4F-VSS0GGK=cRVE30stQBHD_6xu2upWUP1hob488w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello Fabrice,
I'm wondering if you had a chance to reproduce the problem. I'm seeing
something similar, but not exactly, so I'm curious if this may be another
manifestation of the error I get.
Thanks
Nick
On Thu, Feb 19, 2026 at 8:27 AM Fabrice Chapuis <fabrice636861(at)gmail(dot)com>
wrote:
> I could try to reproduce the problem. I'll keep you in touch
>
>>
>> --
>> Robert Haas
>> EDB: http://www.enterprisedb.com
>>
>
I use Postgres 17.7 and I have configured incremental backup
>
> wal_summary_keep_time=10d
> show wal_summary_keep_time=on
>
> On the standby, this message is written every 10 seconds by the
> walsummarizer process.
>
> 2026-02-17 11:40:22.548 CET [544677]: [297-1]
> user=,db=,client=,application= ERROR: could not read WAL from timeline 6
> at 698/460000A0: invalid record length at 698/460000A0: expected at least
> 24, got 0
> 2026-02-17 11:40:32.559 CET [544677]: [298-1]
> user=,db=,client=,application= ERROR: could not read WAL from timeline 6
> at 698/460000A0: invalid record length at 698/460000A0: expected at least
> 24, got 0
>
--
Nick Ivanov
Solutions Architect
www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Burd | 2026-07-13 16:26:23 | Re: Tepid: selective index updates for heap relations |
| Previous Message | Jelte Fennema-Nio | 2026-07-13 15:57:48 | Re: psql single-step mode woes |