On Tue, Sep 17, 2013 at 3:30 AM, Thom Brown <t...@linux.com> wrote: > On 17 September 2013 07:20, Jaime Casanova <ja...@2ndquadrant.com> wrote: >> >> On Mon, Sep 16, 2013 at 3:47 AM, Thom Brown <t...@linux.com> wrote: >> > On 15 September 2013 01:14, Alvaro Herrera <alvhe...@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) >> > > I'm able to run ANALYSE manually without it dying: >
try inserting some data before the ANALYZE, that will force a resumarization which is mentioned in the stack trace of the failure -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
