Re: Minmax indexes - Mailing list pgsql-hackers

From Thom Brown
Subject Re: Minmax indexes
Date
Msg-id CAA-aLv4EyADS-+x9XYf1KMz_r7Lne-58WTeYDwNF9S6iEWMobw@mail.gmail.com
Whole thread Raw
In response to Re: Minmax indexes  (Jaime Casanova <jaime@2ndquadrant.com>)
Responses Re: Minmax indexes
List pgsql-hackers
On 17 September 2013 07:20, Jaime Casanova <jaime@2ndquadrant.com> wrote:
On Mon, Sep 16, 2013 at 3:47 AM, Thom Brown <thom@linux.com> wrote:
> On 15 September 2013 01:14, Alvaro Herrera <alvherre@2ndquadrant.com> wrote:
>>
>> Hi,
>>
>> Here's a reviewable version of what I've dubbed Minmax indexes.
>>
> Thanks for the patch, but I seem to have immediately hit a snag:
>
> pgbench=# CREATE INDEX minmaxtest ON pgbench_accounts USING minmax (aid);
> PANIC:  invalid xlog record length 0
>

fwiw, this seems to be triggered by ANALYZE.
At least i can trigger it by executing ANALYZE on the table (attached
is a stacktrace of a backend exhibiting the failure)

Another thing is this messages i got when compiling:
"""
mmxlog.c: In function ‘minmax_xlog_revmap_set’:
mmxlog.c:161:14: warning: unused variable ‘blkno’ [-Wunused-variable]
bufpage.c: In function ‘PageIndexDeleteNoCompact’:
bufpage.c:1066:18: warning: ‘lastused’ may be used uninitialized in
this function [-Wmaybe-uninitialized]
"""

I'm able to run ANALYSE manually without it dying:

pgbench=# analyse pgbench_accounts;
ANALYZE
pgbench=# analyse pgbench_accounts;
ANALYZE
pgbench=# create index minmaxtest on pgbench_accounts using minmax (aid);
PANIC:  invalid xlog record length 0

--
Thom

pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: PostgreSQL 9.3 beta breaks some extensions "make install"
Next
From: Jeevan Chalke
Date:
Subject: Re: PL/pgSQL, RAISE and error context