| From: | Thom Brown <thom(at)linux(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Minmax indexes |
| Date: | 2013-09-17 21:17:17 |
| Message-ID: | CAA-aLv5awuPj_KRqiqbZCB6x2taHW9-byvxxBNoTEJ3atCBW4w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 17 September 2013 22:03, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> Thom Brown wrote:
>
> Thanks for testing.
>
> > 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
>
> Silly mistake I had already made in another patch. Here's an
> incremental patch which fixes this bug. Apply this on top of previous
> minmax-1.patch.
>
Thanks.
Hit another issue with exactly the same procedure:
pgbench=# create index minmaxtest on pgbench_accounts using minmax (aid);
ERROR: lock 176475 is not held
--
Thom
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Erik Rijkers | 2013-09-17 21:27:20 | Re: Minmax indexes |
| Previous Message | Alvaro Herrera | 2013-09-17 21:03:10 | Re: Minmax indexes |