Re: Tricky bugs in concurrent index build - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Tricky bugs in concurrent index build
Date
Msg-id 22626.1156509725@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tricky bugs in concurrent index build  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Tricky bugs in concurrent index build
List pgsql-hackers
Gregory Stark <stark@enterprisedb.com> writes:
> Because of the way the AM API works changing how the initial heap scan works
> is a bit of a pain. It would require either having some global state or
> passing the concurrent flag through the AM methods or alternatively having a
> whole new AM method.

Yeah, I dealt with that by adding a 'concurrent build' flag to IndexInfo.
A bit grotty but it beats changing a lot of function signatures.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Chahine Hamila
Date:
Subject: integration of pgcluster into postgresql
Next
From: Tom Lane
Date:
Subject: Re: Performance testing of COPY (SELECT) TO