On Thu, Nov 19, 2026 at 7:01 PM Michael Paquier <[email protected]> wrote: > > On Tue, Nov 17, 2026 at 11:20:54PM +0800, Zhijie Hou wrote: > > I think we also need to increase shared_buffers (e.g., to 16MB), because > > $node->init(allows_streaming => 1) sets shared_buffers to 1MB internally, > > causing the pg_class pages to be evicted from shared_buffers before CREATE > > TABLE runs, so the test could not reach the old bug path. > > If we care about this level of tuning, I'd suspect that just bumping > shared_buffers if the wal_consistency_checking switch is enabled > would be fine to do instead of having a buildfarm member that uses a > custom configuration file. wal_consistency_checking consumes a lot of > resources, so this would not hurt more. Your ideas around lifting > some of the masking of the VM pages would make that more valuable in > the long run, as least it seems so to me.
We actually needed the increased shared_buffers to preserve the regression coverage of the original test unrelated to wal_consistency_checking. - Melanie
