From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
---|---|
To: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
Cc: | "x4mmm(at)yandex-team(dot)ru" <x4mmm(at)yandex-team(dot)ru>, "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-27 21:29:08 |
Message-ID: | 7B897E08-76BB-4CDF-948E-92770E7F746C@amazon.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Here is a rebased version of my patch. As before, I'm not yet
handling replication, archive_timeout, and persisting latest-marked-
ready through crashes. If this approach seems reasonable to others,
I'll go ahead and start working on these items.
Nathan
Attachment | Content-Type | Size |
---|---|---|
0001-WIP-Avoid-marking-segments-as-ready-for-archival-too.patch | application/octet-stream | 10.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Justin Pryzby | 2021-01-27 21:35:03 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |
Previous Message | Alexey Kondratov | 2021-01-27 21:19:06 | Re: Allow CLUSTER, VACUUM FULL and REINDEX to change tablespace on the fly |