Re: Bug in ginRedoRecompress that causes opaque data on page to be overrun

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "R, Siva" <sivasubr(at)amazon(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bug in ginRedoRecompress that causes opaque data on page to be overrun
Date: 2018-09-04 21:55:14
Message-ID: CAH2-WzneRxhYubPMh-x0L7h_1iH5kddVH5HWx2RFWKh=ELdgzw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Sep 4, 2018 at 12:59 PM, R, Siva <sivasubr(at)amazon(dot)com> wrote:
> We recently encountered an issue where the opaque data flags on a gin data
> leaf page was corrupted while replaying a gin insert WAL record. Upon
> further examination of the redo code, we found a bug in ginRedoRecompress
> code, which extracts the WAL information and updates the page.

I wonder how you managed to detect it in the first place. Were you
using something like wal_consistency_checking=all, with a custom
stress-test?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-09-04 22:02:51 Re: test_pg_dump missing cleanup actions
Previous Message Tom Lane 2018-09-04 21:46:29 Re: Bug fix for glibc broke freebsd build in REL_11_STABLE