From: "R, Siva" <sivasubr@amazon.com>
To: Peter Geoghegan <pg@bowt.ie>,
        Alexander Korotkov
	<a.korotkov@postgrespro.ru>
CC: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: Bug in ginRedoRecompress that causes opaque data on page to be
 overrun
Thread-Topic: Bug in ginRedoRecompress that causes opaque data on page to be
 overrun
Thread-Index: AQHURITWziSocye1S0ygUmXh1SVXsaTgquEAgAANUlE=
Date: Tue, 4 Sep 2018 22:45:17 +0000
Message-ID: <1536101117759.63175@amazon.com>
References: 
 <1536091151804.6588@amazon.com>,<CAH2-WzneRxhYubPMh-x0L7h_1iH5kddVH5HWx2RFWKh=ELdgzw@mail.gmail.com>
In-Reply-To: 
 <CAH2-WzneRxhYubPMh-x0L7h_1iH5kddVH5HWx2RFWKh=ELdgzw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Precedence: Bulk
Precedence: bulk

Hi Alexander!=0A=
On Tue, Sep 4, 2018 at 09:16 PM, Alexander Korotkov <a.korotkov@postgrespro=
.ru> wrote:=0A=
> Do you have a test scenario for reproduction of this issue?  We need=0A=
> it to ensure that fix is correct.=0A=
=0A=
Unfortunately, I do not have a way of reproducing this issue.=0A=
So far I have tried a workload consisting of inserts (of the=0A=
same attribute value that is indexed), batch deletes of rows=0A=
and vacuum interleaved with engine crash/restarts.=0A=
=0A=
Hi Peter!=0A=
On Tue, Sep 4, 2018 at 09:55 PM, Peter Geoghegan <pg@bowt.ie> wrote:=0A=
> I wonder how you managed to detect it in the first place. Were you=0A=
> using something like wal_consistency_checking=3Dall, with a custom=0A=
> stress-test?=0A=
=0A=
We observed this corruption during stress testing and were=0A=
able to isolate the corrupted page and WAL record changes=0A=
leading up to the corruption using some internal diagnostic=0A=
tools.=0A=
=0A=
Best=0A=
Siva=