| From: | James Coleman <jtc331(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, David Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: [DOC] Document concurrent index builds waiting on each other |
| Date: | 2021-01-13 15:16:27 |
| Message-ID: | CAAaqYe-P54OQOm1u+dWkD=DO7eGAdMBTSVygj_JvqDjibXih3Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 13, 2021 at 12:58 AM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Tue, Jan 12, 2021 at 04:51:39PM -0300, Alvaro Herrera wrote:
> > I looked into this again, and I didn't like what I had added to
> > maintenance.sgml at all. It seems out of place where I put it; and I
> > couldn't find any great spots. Going back to your original proposal,
> > what about something like this? It's just one more para in the "notes"
> > section in CREATE INDEX and REINDEX pages, without any additions to the
> > VACUUM pages.
>
> +1.
I think one more para in the notes is good. But shouldn't we still
clarify the issue is specific to CONCURRENTLY?
Also that it's not just the table being indexed seems fairly significant.
How about something like:
---
Like any long-running transaction, <command>REINDEX CONCURRENTLY</command> can
affect which tuples can be removed by concurrent
<command>VACUUM</command> on any table.
---
James
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-13 15:28:26 | Re: Alter timestamp without timezone to with timezone rewrites rows |
| Previous Message | David G. Johnston | 2021-01-13 15:01:37 | Re: Alter timestamp without timezone to with timezone rewrites rows |