pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Tom Lane <tgl@sss.pgh.pa.us>
To: Thomas Munro <thomas.munro@gmail.com>
Cc: Peter Geoghegan <pg@bowt.ie>
Cc: Andres Freund <andres@anarazel.de>
Cc: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Andrew Dunstan <andrew@dunslane.net>
Cc: Michael Paquier <michael@paquier.xyz>
Cc: Anastasia Lubennikova <lubennikovaav@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: A test for replay of regression tests
Date: Sat, 02 Apr 2022 01:10:39 -0400
Message-ID: <1258185.1648876239@sss.pgh.pa.us> (raw )
In-Reply-To: <CA+hUKGLV3wzmYFbNs+TZ1+w0e=hc61fcvrF3OmutuaPBuZMd0w@mail.gmail.com >
References: <CA+hUKG+Bncrfh0piJ83HUZ4cG+58TikGXwDux4sj7jvoMc=eNg@mail.gmail.com >
<CA+hUKGK-q9utvxorA8sCwF3S4SzBmxxDgneP4rLqeHWdZxM4Gg@mail.gmail.com >
<CA+hUKGLsrWbiCcMxBLRBAP6Z=ykFRHWzdmP9YKujSKoSnEJECQ@mail.gmail.com >
<b10198e2-7411-7946-dfaa-3c8c5525d5c9@dunslane.net >
<CA+hUKGKMd24n_Uau_HfKRhzARLgOm-_BbvqK4S6SY3Q=Kq=MCA@mail.gmail.com >
<CAD21AoCNoWjYkdEtr+VDoF9v__V905AedKZ9iF=ArgCtrbxZqw@mail.gmail.com >
<CA+hUKGKRtpz3qAg7=Yne_oJ8ZdeiT3JbPPCayjgHFgrKUeKViQ@mail.gmail.com >
<CAH2-Wzk3RYzqdaOs5PUqoUjd=_LbWc7zdDzV6rR6D3kM3C=fNg@mail.gmail.com >
<CA+hUKGJm_uex8rDfTcP6ig_nNTySD9DOKq9iyghTtuE0dg+t7g@mail.gmail.com >
<CAH2-Wzm_mXH2mxn150tPmh1_kjQ9eC2dKdEr=UtHVOjnS2x3Sg@mail.gmail.com >
<20220325041607.3vcnw34wxoucb5zy@alap3.anarazel.de >
<CAH2-WznxZDjHaxYk2u_wpJysQGBLiVxCa550Ja7xxHm-+eTVNw@mail.gmail.com >
<CA+hUKGLV3wzmYFbNs+TZ1+w0e=hc61fcvrF3OmutuaPBuZMd0w@mail.gmail.com >
Thomas Munro <thomas.munro@gmail.com> writes:
> cfbot found another source of nondeterminism in the regression tests,
> due to the smaller shared_buffers used in this TAP test:
This failure seems related but not identical:
https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=myna&dt=2022-04-02%2004%3A00%3A26
portals.out is expecting that the "foo25ns" cursor will read
starting at the beginning of tenk1, but it's starting somewhere
else, which presumably is a syncscan effect.
I think the fundamental instability here is that this TAP test is
setting shared_buffers small enough to allow the syncscan logic
to kick in where it does not in normal testing. Maybe we should
just disable syncscan in this test script?
regards, tom lane
view thread (82+ messages) latest in thread
Message-ID: <1258185.1648876239@sss.pgh.pa.us>
Permalink: ../1258185.1648876239@sss.pgh.pa.us/
Also on: postgresql.org/message-id/1258185.1648876239@sss.pgh.pa.us
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us, thomas.munro@gmail.com, pg@bowt.ie, andres@anarazel.de, sawada.mshk@gmail.com, andrew@dunslane.net, michael@paquier.xyz, lubennikovaav@gmail.com
Subject: Re: A test for replay of regression tests
In-Reply-To: <1258185.1648876239@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox