Re: Support for REINDEX CONCURRENTLY - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Support for REINDEX CONCURRENTLY
Date
Msg-id CAB7nPqTgA_8VDf9WQd-+NTu3OUf549Qb+0Sxw2vw-_fCZ_9=EA@mail.gmail.com
Whole thread Raw
In response to Re: Support for REINDEX CONCURRENTLY  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: Support for REINDEX CONCURRENTLY
List pgsql-hackers
On Wed, Jul 3, 2013 at 5:22 AM, Fujii Masao <masao.fujii@gmail.com> wrote:
> Why did you remove the check of indisvalid from the --binary-upgrade SQL?
> Without this check, if there is the invalid toast index, more than one rows are
> returned and ExecuteSqlQueryForSingleRow() would cause the error.
>
> +       foreach(lc, indexlist)
> +               *toastidxs[i++] = index_open(lfirst_oid(lc), lock);
>
> *toastidxs[i++] should be (*toastidxs)[i++]. Otherwise, segmentation fault can
> happen.
>
> For now I've not found any other big problem except the above.
OK cool, updated version attached. If you guys think that the attached
version is fine (only the reltoasyidxid removal part), perhaps it
would be worth committing it as Robert also committed the MVCC catalog
patch today. So we would be able to focus on the core feature asap
with the 2nd patch, and the removal of AccessExclusiveLock at swap
step.

Regards,
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: preserving forensic information when we freeze
Next
From: Fujii Masao
Date:
Subject: Re: Support for REINDEX CONCURRENTLY