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

David G. Johnston <david.g.johnston@gmail.com>

From: "David G. Johnston" <david.g.johnston@gmail.com>

To: Michael Paquier <michael@paquier.xyz>

Cc: James Coleman <jtc331@gmail.com>, PostgreSQL Developers <pgsql-hackers@lists.postgresql.org>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@2ndquadrant.com>

Date: 2020-10-21T22:32:19Z

Lists: pgsql-hackers

Attachments

v3-0001-Document-concurrent-indexes-waiting-on-each-other.patch (application/octet-stream) patch v3-0001
v4-0002-Document-vacuum-on-one-table-depending-on-concurr.patch (application/octet-stream) patch v4-0002

On Wed, Oct 21, 2020 at 3:25 PM David G. Johnston <
david.g.johnston@gmail.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.

Commits

Call out vacuum considerations in create index docs
- c285a244f6d3 13.2 landed
- 93c39f987e9c 14.0 landed
- 259b21233032 12.6 landed
Document concurrent indexes waiting on each other
- ed9c9b033546 11.11 landed
- d3bd36a63d69 10.16 landed
- b3d33bf598dd 9.6.21 landed
- b2603f16ad75 12.6 landed
- 968a537b432e 9.5.25 landed
- 58ebe967f8a1 14.0 landed
- 3fe0e7c3fa27 13.2 landed
snapshot scalability: Don't compute global horizons while building snapshots.
- dc7420c2c927 14.0 cited
Remove PROC_IN_ANALYZE and derived flags
- cea3d5589865 14.0 landed
Improve performance of get_actual_variable_range with recently-dead tuples.
- 3ca930fc39cc 11.0 cited