Re: GIN data corruption bug(s) in 9.6devel

From: Teodor Sigaev <teodor(at)sigaev(dot)ru>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: GIN data corruption bug(s) in 9.6devel
Date: 2016-04-15 16:26:33
Message-ID: 57111639.1030801@sigaev.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>> Alvaro's recommendation, to let the cleaner off the hook once it
>> passes the page which was the tail page at the time it started, would
>> prevent any process from getting pinned down indefinitely, but would
> Added, see attached patch (based on v3.1)
If there is no objections I will aplly it at mondeay and backpatch all supported
versions.

--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2016-04-15 16:27:30 Re: EXPLAIN VERBOSE with parallel Aggregate
Previous Message Ashutosh Bapat 2016-04-15 16:16:10 Re: Odd system-column handling in postgres_fdw join pushdown patch