| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Andrey Klychkov <aaklychkov(at)mail(dot)ru>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Re[2]: |
| Date: | 2020-05-28 13:14:20 |
| Message-ID: | 6214.1590671660@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)xyz> writes:
> I don't think we should have any duplication between the REINDEX and
> reindexdb pages, and we have that in reindexdb:
> --concurrently
> Use the CONCURRENTLY option. See REINDEX for further information.
> An idea would be to append to the second sentence something like
> "where all the caveats of this option are explained in details"?
+1, but I'd change the whole sentence. Maybe
Use the CONCURRENTLY option. See REINDEX, where all the caveats of
this option are explained in detail.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jawarilal, Manish | 2020-05-28 15:30:55 | pgbench bug / limitation |
| Previous Message | Michael Paquier | 2020-05-28 07:12:53 | Re: BUG #16468: Doc: release note 13, missing GUC enable_groupingsets_hash_disk |