Horton

Re: Deadlock between concurrent index builds on different tables

Alban Hertroys <haramrae@gmail.com>

View thread View on postgr.es
From: Alban Hertroys <haramrae@gmail.com>
To: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Jeremy Finzel <finzelj@gmail.com>, Jeff Janes <jeff.janes@gmail.com>, Postgres General <pgsql-general@postgresql.org>
Date: 2017-12-26T23:27:05Z
Lists: pgsql-general 
> On 26 Dec 2017, at 18:11, Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:

…

> 3. configure and make
>   ./configure <configure options>
>   make
>   make install

…

> For the options in step 3 you could use whatever your current server
> has; use "pg_config --configure" to find these out.  You're gonna need
> same flags if you want to use your existing data directory.

Does that mean that at step 3 one could issue this?:

./configure `pg_config —configure`

If I had the sources at hand, I'd try that myself, but I don't and getting those is frankly a bit of a hassle to just test out whether that works ;)

Alban Hertroys
--
If you can't see the forest for the trees,
cut the trees and you'll find there is no forest.

Commits

  1. Fix deadlock hazard in CREATE INDEX CONCURRENTLY