Re: Deadlock between concurrent index builds on different tables
Michael Paquier <michael.paquier@gmail.com>
From: Michael Paquier <michael.paquier@gmail.com>
To: Alban Hertroys <haramrae@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Jeremy Finzel <finzelj@gmail.com>, Jeff Janes <jeff.janes@gmail.com>, Postgres General <pgsql-general@postgresql.org>
Date: 2017-12-27T00:43:03Z
Lists: pgsql-general
On Wed, Dec 27, 2017 at 12:27:05AM +0100, Alban Hertroys wrote: > >> 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 ;) For this issue I don't think that you are going to care much about dependencies with low-level libraries like SSL or such as the behavior is in integrality linked with PostgreSQL internals and the physical representation of how transactions are handled with system catalogs. In short there is no need to be fancy :) -- Michael
Commits
-
Fix deadlock hazard in CREATE INDEX CONCURRENTLY
- fb7b43903e91 9.6.7 landed
- 82f1c3b7d1e0 9.5.11 landed
- 6d2a9ae0ed17 10.2 landed
- 54eff5311d7c 11.0 landed
- 47a3a1317873 9.4.16 landed