Postgres Pro
Downloads
Home   >   mailing lists

Re: BRIN indexes - TRAP: BadArgument - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: BRIN indexes - TRAP: BadArgument
Date
Msg-id CAMkU=1xQkEB-QzACbsb2yyO5Rfnu6ibuBVg762-z4g60RtNtrA@mail.gmail.com
Whole thread Raw
In response to Re: BRIN indexes - TRAP: BadArgument  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: BRIN indexes - TRAP: BadArgument  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Tree view
On Mon, Nov 3, 2014 at 2:18 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:

So here's v21.  I also attach a partial diff from v20, just in case
anyone wants to give it a look.

This needs a bump to 1.3, or the extension won't install:

contrib/pageinspect/pageinspect.control


During crash recovery, I am getting a segfault:

#0  0x000000000067ee35 in LWLockRelease (lock=0x0) at lwlock.c:1161
#1  0x0000000000664f4a in UnlockReleaseBuffer (buffer=0) at bufmgr.c:2888
#2  0x0000000000465a88 in brin_xlog_revmap_extend (lsn=<value optimized out>, record=<value optimized out>) at brin_xlog.c:261
#3  brin_redo (lsn=<value optimized out>, record=<value optimized out>) at brin_xlog.c:284
#4  0x00000000004ce505 in StartupXLOG () at xlog.c:6795

I failed to preserve the data directory, I'll try to repeat this later this week if needed.
 
Cheers,

Jeff

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: What exactly is our CRC algorithm?
Next
From: Alexey Vasiliev
Date:
Subject: Re[2]: [HACKERS] Patch: add recovery_timeout option to control timeout of restore_command nonzero status code