From: Tom Lane <tgl@sss.pgh.pa.us>
To: Kyotaro Horiguchi <horikyota.ntt@gmail.com>
Cc: thomas.munro@gmail.com
Cc: pg@bowt.ie
Cc: pgsql-hackers@lists.postgresql.org
Cc: craig.ringer@enterprisedb.com
Cc: robertmhaas@gmail.com
Subject: Re: 011_crash_recovery.pl intermittently fails
Date: Fri, 05 Mar 2021 11:16:55 -0500
Message-ID: <1495174.1614961015@sss.pgh.pa.us> (raw)
In-Reply-To: <20210305.180819.844001367516475145.horikyota.ntt@gmail.com>
References: <CA+hUKGK50B4soLLa=Vjt58m=GcYtTve7uSGbEEa6dj6GRExAFQ@mail.gmail.com>
<1439485.1614919234@sss.pgh.pa.us>
<20210305.165117.1192284154251506643.horikyota.ntt@gmail.com>
<20210305.180819.844001367516475145.horikyota.ntt@gmail.com>
Kyotaro Horiguchi <horikyota.ntt@gmail.com> writes:
> So I think we need to remove the shared_buffers setting for the
> allows_streamig case in PostgresNode.pm
That would have uncertain effects on other TAP tests, so I'm disinclined
to do it that way. 011_crash_recovery.pl doesn't actually use a standby
server, so just removing its use of the allows_streaming option seems
sufficient.
But, of course, first we need a fix for the bug we now know exists.
Was anyone volunteering to make the patch?
regards, tom lane
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, horikyota.ntt@gmail.com, thomas.munro@gmail.com, pg@bowt.ie, pgsql-hackers@lists.postgresql.org, craig.ringer@enterprisedb.com, robertmhaas@gmail.com
Subject: Re: 011_crash_recovery.pl intermittently fails
In-Reply-To: <1495174.1614961015@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