Re: BRIN indexes - TRAP: BadArgument

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Emanuel Calvo <3manuek(at)esdebian(dot)org>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Nicolas Barbier <nicolas(dot)barbier(at)gmail(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: BRIN indexes - TRAP: BadArgument
Date: 2014-11-04 00:16:08
Message-ID: CAMkU=1zN1W3_Gbc7wFxU7pycX1gxEk37zx9K71u5+XE+MkKx1w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Nov 3, 2014 at 2:18 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
wrote:

> Robert Haas wrote:
> > [lots]
>
> I have fixed all these items in the attached, thanks -- most
> user-visible change was the pageinspect 1.3 thingy. pg_upgrade from 1.2
> works fine now. I also fixed some things Heikki noted, mainly avoid
> retail pfree where possible, and renumber the support procs to leave
> room for future expansion of the framework. XLog replay code is updated
> too.
>
> Also, I made the summarization step callable directly from SQL without
> having to invoke VACUUM.
>
> So here's v21. I also attach a partial diff from v20, just in case
> anyone wants to give it a look.
>

I get a couple compiler warnings with this:

brin.c: In function 'brininsert':
brin.c:97: warning: 'tupcxt' may be used uninitialized in this function
brin.c:98: warning: 'oldcxt' may be used uninitialized in this function

Also, I think it is missing a cat version bump. It let me start the
patched server against an unpatched initdb run, but once started it didn't
find the index method.

What would it take to make CLUSTER work on a brin index? Now I just added
a btree index on the same column, clustered on that, then dropped that
index.

Thanks,

Jeff

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Josh Berkus 2014-11-04 00:49:36 pg_multixact not getting truncated
Previous Message Mikko Tiihonen 2014-11-03 23:56:22 Re: Pipelining executions to postgresql server