| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Andrey Borodin <x4mmm(at)yandex-team(dot)ru>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
| Cc: | "a(dot)lubennikova(at)postgrespro(dot)ru" <a(dot)lubennikova(at)postgrespro(dot)ru>, "hlinnaka(at)iki(dot)fi" <hlinnaka(at)iki(dot)fi>, "matsumura(dot)ryo(at)fujitsu(dot)com" <matsumura(dot)ryo(at)fujitsu(dot)com>, "masao(dot)fujii(at)gmail(dot)com" <masao(dot)fujii(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: archive status ".ready" files may be created too early |
| Date: | 2021-01-26 19:31:04 |
| Message-ID: | 5C763C5F-C866-4622-88F3-7DC4A46D29D3@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/2/21, 8:55 AM, "Andrey Borodin" <x4mmm(at)yandex-team(dot)ru> wrote:
> Recently we had somewhat related incident. Do I understand correctly that this incident is related to the bug discussed in this thread?
I'm not sure that we can rule it out, but the log pattern I've
typically seen for this is "invalid contrecord length." The issue is
that we're marking segments as ready for archive when the segment is
fully written versus when its WAL records are fully written (since its
WAL records may cross into the next segment). The fact that you're
seeing zeroes at the end of your archived segments leads me to think
it is unlikely that you are experiencing this bug.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2021-01-26 19:41:58 | Re: making update/delete of inheritance trees scale better |
| Previous Message | Bossart, Nathan | 2021-01-26 19:13:57 | Re: archive status ".ready" files may be created too early |