| From: | Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
| Cc: | thomas(dot)munro(at)gmail(dot)com, pg(at)bowt(dot)ie, pgsql-hackers(at)lists(dot)postgresql(dot)org, craig(dot)ringer(at)enterprisedb(dot)com, robertmhaas(at)gmail(dot)com |
| Subject: | Re: 011_crash_recovery.pl intermittently fails |
| Date: | 2021-03-05 09:08:19 |
| Message-ID: | 20210305.180819.844001367516475145.horikyota.ntt@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At Fri, 05 Mar 2021 16:51:17 +0900 (JST), Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com> wrote in
> The difference comes from the difference of shared_buffers. In the
> "allows_streaming" case, PostgresNode::init() *reduces* the number
> down to '1MB'(128 blocks) which leads to only 8 XLOGbuffers, which
> will very soon be wrap-arounded, which leads to XLogWrite.
>
> When allows_streaming=0 case, the default size of shared_buffers is
> 128MB (16384 blocks). WAL buffer (512) doesn't get wrap-arounded
> during the test and no WAL buffer is written out in that case.
So I think we need to remove the shared_buffers setting for the
allows_streamig case in PostgresNode.pm
regards.
--
Kyotaro Horiguchi
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-03-05 09:14:49 | Re: PROXY protocol support |
| Previous Message | Fujii Masao | 2021-03-05 09:07:05 | Re: n_mod_since_analyze isn't reset at table truncation |