Horton
Menu

Re: Support for REINDEX CONCURRENTLY

Fujii Masao <masao.fujii@gmail.com>

View thread
From: Fujii Masao <masao.fujii@gmail.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Andres Freund <andres@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Simon Riggs <simon@2ndquadrant.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>
Date: 2013-02-28T14:26:40Z
Lists: pgsql-hackers 
On Thu, Feb 28, 2013 at 3:21 PM, Michael Paquier
<michael.paquier@gmail.com> wrote:
> Andres, Masao, do you need an extra round or review or do you think this is
> ready to be marked as committer?
> On my side I have nothing more to add to the existing patches.

Sorry for the late reply.

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;

Regards,

-- 
Fujii Masao

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Background worker processes

  2. Fix assorted bugs in CREATE/DROP INDEX CONCURRENTLY.

  3. Work around unportable behavior of malloc(0) and realloc(NULL, 0).

  4. Properly set relpersistence for fake relcache entries.