| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | alvherre(at)alvh(dot)no-ip(dot)org, jeff(dot)janes(at)gmail(dot)com, mk(at)071(dot)ovh, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size |
| Date: | 2021-07-29 07:50:07 |
| Message-ID: | 20210729.165007.1956564330541804824.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
(Somehow the previous mail was broken in many ways. I re-send it.)
At Thu, 29 Jul 2021 16:20:38 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> So it seems to me we need to explicitly prevent unexpected checkpoints
> from happening maybe by enlarging max_wal_size temporily.
>
> I'll going that way.
I ended up with the attached. It causes a checkpoint reliably exactly
at the aimed timing without.
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Make-slot-test-more-stable.patch | text/x-patch | 1.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrey Borodin | 2021-07-29 12:30:56 | Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data |
| Previous Message | Kyotaro Horiguchi | 2021-07-29 07:45:40 | Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size |