From: | Jaime Casanova <jaime(at)2ndquadrant(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Minmax indexes |
Date: | 2013-09-17 06:20:17 |
Message-ID: | CAJKUy5h+fHSB_VaTa2-mgGpnsN0hudqRGmJNrgghs7VsygAL+w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Sep 16, 2013 at 3:47 AM, Thom Brown <thom(at)linux(dot)com> wrote:
> On 15 September 2013 01:14, Alvaro Herrera <alvherre(at)2ndquadrant(dot)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]
"""
--
Jaime Casanova www.2ndQuadrant.com
Professional PostgreSQL: Soporte 24x7 y capacitación
Phone: +593 4 5107566 Cell: +593 987171157
Attachment | Content-Type | Size |
---|---|---|
stacktrace.txt | text/plain | 3.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Samrat Revagade | 2013-09-17 06:45:56 | Re: Patch for fail-back without fresh backup |
Previous Message | Peter Eisentraut | 2013-09-17 03:51:01 | Re: [PATCH] Add an ldapoption to disable chasing LDAP referrals |