Re: Support for REINDEX CONCURRENTLY

Fujii Masao <masao.fujii@gmail.com>

From: Fujii Masao <masao.fujii@gmail.com>

To: Andres Freund <andres@2ndquadrant.com>

Cc: Michael Paquier <michael.paquier@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-07-03T17:41:45Z

Lists: pgsql-hackers

Attachments

20130704_1_remove_reltoastidxid_v18.patch (application/octet-stream) patch v18

On Thu, Jul 4, 2013 at 2:36 AM, Andres Freund <andres@2ndquadrant.com> wrote:
> On 2013-07-04 02:32:32 +0900, Michael Paquier wrote:
>> > Wouldn't it make more sense to fetch the toast index oid in the query
>> > ontop instead of making a query for every relation?

+1
I changed the query that way. Updated version of the patch attached.

Also I updated the rules.out because Michael changed the system_views.sql.
Otherwise, the regression test would fail.

Will commit this patch.

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 →

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