Re: Support for REINDEX CONCURRENTLY

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>

To: Michael Paquier <michael.paquier@gmail.com>

Cc: Fujii Masao <masao.fujii@gmail.com>, 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-03-01T21:32:19Z

Lists: pgsql-hackers

REINDEX CONCURRENTLY resets the statistics in pg_stat_user_indexes,
whereas plain REINDEX does not.  I think they should be preserved in
either case.

Commits

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

Background worker processes
- da07a1e85651 9.3.0 cited
Fix assorted bugs in CREATE/DROP INDEX CONCURRENTLY.
- 3c84046490be 9.3.0 cited
Work around unportable behavior of malloc(0) and realloc(NULL, 0).
- 09ac603c36d1 9.3.0 cited
Properly set relpersistence for fake relcache entries.
- beb850e1d873 9.3.0 cited