| From: | Srinath Reddy Sadipiralla <srinath2133(at)gmail(dot)com> |
|---|---|
| To: | João Rito <joaovictor(dot)rito(at)gmail(dot)com> |
| Cc: | David Shorten <shortenda(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Standby stuck after walreceiver restart just before a WAL segment boundary |
| Date: | 2026-11-11 13:51:42 |
| Message-ID: | CAFC+b6o=35jgVN_b5GBpE4-Q5q7Miy0CkDsvSn2q8T03dHFVZw@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi João,
On Tue, Nov 10, 2026 at 11:03 AM João Rito <joaovictor(dot)rito(at)gmail(dot)com>
wrote:
>
> 3. On the test, Srinath suggested truncating the standby's copy of the last
> segment by 8 bytes instead of padding with a retry loop. I like the idea of
> a deterministic setup, but I am not sure it works as described. WAL segment
> files are always full size, and I think a short segment file makes the
> standby fail with an error when it reads it, instead of showing the
> boundary
> case. Zeroing the last 8 bytes instead of truncating might work better.
Thanks, this is what I also intended to say but somehow missed about 0ing.
--
Thanks :)
Srinath Reddy Sadipiralla
EDB: https://www.enterprisedb.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2026-11-11 14:02:26 | Re: pgbench --unlogged-tables silently ignored for branches/tellers/history when --partitions is used |
| Previous Message | Hayato Kuroda (Fujitsu) | 2026-11-11 13:50:41 | RE: Injection point: fix race condition between attach and cleanup |