Quick Links

Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM

From:	Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To:	Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc:	Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org>
Subject:	Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM
Date:	2017-11-03 20:34:48
Message-ID:	4434.1509741288@sss.pgh.pa.us
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> With this v3 patch (assuming this is the one you just committed
> as ec42a1dcb30de235b252f6d4) am now getting make check failures.

There's a followup commit already :-(

regards, tom lane

In response to

Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM at 2017-11-03 20:18:23 from Jeff Janes

Responses

Re: Re: PANIC: invalid index offnum: 186 when processing BRIN indexes in VACUUM at 2017-11-03 21:51:11 from Jeff Janes

Browse pgsql-hackers by date

	From	Date	Subject
Next Message	Tom Lane	2017-11-03 21:23:37	Re: Small improvement to compactify_tuples
Previous Message	Andres Freund	2017-11-03 20:33:45	Re: [HACKERS] pgsql: Fix freezing of a dead HOT-updated tuple