| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se> |
| Subject: | Re: "Routine Reindexing" docs should be updated to reference REINDEX CONCURRENTLY |
| Date: | 2019-04-26 14:53:35 |
| Message-ID: | 7959.1556290415@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> On Thu, Apr 25, 2019 at 01:34:41PM -0700, Peter Geoghegan wrote:
>> The documentation has a section called "Routine Reindexing", which
>> explains how to simulate REINDEX CONCURRENTLY with a sequence of
>> creation and replacement steps. This should be updated to reference
>> the REINDEX CONCURRENTLY command.
> Agreed, good catch. I would suggest to remove most of the section and
> just replace it with a reference to REINDEX CONCURRENTLY, as per the
> attached. What do you think?
+1. Maybe say "... which requires only a
<literal>SHARE UPDATE EXCLUSIVE</literal> lock."
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2019-04-26 15:02:46 | Re: findTargetlistEntrySQL92() and COLLATE clause |
| Previous Message | Tom Lane | 2019-04-26 14:51:36 | Re: REINDEX INDEX results in a crash for an index of pg_class since 9.6 |