Horton
Menu

Re: Support for REINDEX CONCURRENTLY

Andres Freund <andres@2ndquadrant.com>

View thread
From: Andres Freund <andres@2ndquadrant.com>
To: Michael Paquier <michael.paquier@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Fujii Masao <masao.fujii@gmail.com>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Peter Eisentraut <peter_e@gmx.net>, Tom Lane <tgl@sss.pgh.pa.us>, Simon Riggs <simon@2ndquadrant.com>
Date: 2013-10-10T07:38:55Z
Lists: pgsql-hackers 
On 2013-10-02 13:16:06 +0900, Michael Paquier wrote:
> Each patch applied with its parents compiles, has no warnings AFAIK
> and passes regression/isolation tests. Working on 0004 by the end of
> the CF seems out of the way IMO, so I'd suggest focusing on 0002 and
> 0003 now, and I can put some time to finalize them for this CF. I
> think that we should perhaps split 0003 into 2 pieces, with one patch
> for the introduction of index_concurrent_build, and another for
> index_concurrent_set_dead. Comments are welcome about that though, and
> if people agree on that I'll do it once 0002 is finalized.

FWIW I don't think splitting of index_concurrent_build is worthwile...

Greetings,

Andres Freund

-- 
 Andres Freund	                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

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.