From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Support for REINDEX CONCURRENTLY |
Date: | 2013-03-01 03:57:35 |
Message-ID: | CAB7nPqTmOJk1xkGRxx4iOpAf3O1zD5wkZMUArnxNWxo9kKOt0w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Feb 28, 2013 at 11:26 PM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> I found one problem in the latest patch. I got the segmentation fault
> when I executed the following SQLs.
>
> CREATE TABLE hoge (i int);
> CREATE INDEX hogeidx ON hoge(abs(i));
> INSERT INTO hoge VALUES (generate_series(1,10));
> REINDEX TABLE CONCURRENTLY hoge;
>
> The error messages are:
>
> LOG: server process (PID 33641) was terminated by signal 11: Segmentation
> fault
> DETAIL: Failed process was running: REINDEX TABLE CONCURRENTLY hoge;
>
Oops. Index expressions were not correctly extracted when building
columnNames for index_create in index_concurrent_create.
Fixed in this new patch. Thanks for catching that.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
20130301_1_remove_reltoastidxid.patch | application/octet-stream | 37.0 KB |
20130301_2_reindex_concurrently_v14.patch | application/octet-stream | 80.2 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Hunsaker | 2013-03-01 04:42:04 | Re: Memory leakage associated with plperl spi_prepare/spi_freeplan |
Previous Message | Tom Duffey | 2013-03-01 01:55:15 | Re: Floating point error |