Re: [DOC] Document concurrent index builds waiting on each other

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: James Coleman <jtc331(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Subject: Re: [DOC] Document concurrent index builds waiting on each other
Date: 2020-10-21 22:32:19
Message-ID: CAKFQuwZ02mm+rs=4PYHV3_vvub3_0ziV9wnC5xN+HPHNVg_JPA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 21, 2020 at 3:25 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

>
> v3-0002 needs a rebase over the create_index.sgml page due to the change
> of the nearby xref to link. Attached as v4-0002 along with the original
> v3-0001.
>
>
attached...

Reading the commit message on 0002 - vacuum isn't a transaction-taking
command so it wouldn't interfere with itself, create index does use
transactions and thus it's not surprising that it interferes with vacuum -
which looks at transactions, not commands (as most of the internals would
I'd presume).

David J.

Attachment Content-Type Size
v3-0001-Document-concurrent-indexes-waiting-on-each-other.patch application/octet-stream 1.6 KB
v4-0002-Document-vacuum-on-one-table-depending-on-concurr.patch application/octet-stream 815 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message John Naylor 2020-10-21 22:45:44 Re: speed up unicode decomposition and recomposition
Previous Message David G. Johnston 2020-10-21 22:25:51 Re: [DOC] Document concurrent index builds waiting on each other