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

Michael Paquier <michael@paquier.xyz>

From: Michael Paquier <michael@paquier.xyz>

To: Alvaro Herrera <alvherre@2ndquadrant.com>

Cc: Andres Freund <andres@anarazel.de>, James Coleman <jtc331@gmail.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2020-03-26T06:52:38Z

Lists: pgsql-hackers

On Wed, Mar 25, 2020 at 05:12:48PM -0300, Alvaro Herrera wrote:
> Hmm, that sounds more promising.

Haven't looked at that myself in details.  But as I doubt that this
would be backpatched, wouldn't it be better to document the issue for
now?
--
Michael

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