Message-ID: <3031fc19-7540-b8be-e34b-835e6fc4493e@dunslane.net>
Date: Tue, 5 Apr 2022 08:54:35 -0400
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.5.0
Subject: Re: Run pg_amcheck in 002_pg_upgrade.pl and 027_stream_regress.pl?
Content-Language: en-US
To: Peter Geoghegan <pg@bowt.ie>, Andres Freund <andres@anarazel.de>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
 Mark Dilger <mark.dilger@enterprisedb.com>,
 Robert Haas <robertmhaas@gmail.com>
References: <20220403185303.futnxfj64llw4uny@alap3.anarazel.de>
 <CAH2-Wzmfwj_61U8VoSxY-NTiPvAJD7D-aTCO43-+q273oPdq8g@mail.gmail.com>
From: Andrew Dunstan <andrew@dunslane.net>
In-Reply-To: <CAH2-Wzmfwj_61U8VoSxY-NTiPvAJD7D-aTCO43-+q273oPdq8g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Archived-At: <https://www.postgresql.org/message-id/3031fc19-7540-b8be-e34b-835e6fc4493e%40dunslane.net>
Precedence: bulk


On 4/3/22 22:10, Peter Geoghegan wrote:
> On Sun, Apr 3, 2022 at 11:53 AM Andres Freund <andres@anarazel.de> wrote:
>> We've had bugs in pg_upgrade where post-upgrade xid horizons weren't correctly
>> set. We've had bugs were indexes were corrupted during replay.
>>
>> The latter can be caught by wal_consistency_checking - but that's pretty
>> expensive.
>>
>> It seems $subject would have a chance of catching some of these bugs, as well
>> as exposing amcheck to a database with a bit more varied content?
> I thought that Andrew Dunstan (CC'd) had a BF animal that did this
> setup. But I'm not sure if that ever ended up happening.


I don't think any of my BF animals do anything special in this area.


cheers


andrew


--
Andrew Dunstan
EDB: https://www.enterprisedb.com