Re: Deadlock between concurrent index builds on different tables

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Alban Hertroys <haramrae(at)gmail(dot)com>
Cc: Jeremy Finzel <finzelj(at)gmail(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Deadlock between concurrent index builds on different tables
Date: 2017-12-27 13:56:20
Message-ID: 20171227135620.ihv7oyiusyinq5tf@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Alban Hertroys wrote:

> Does that mean that at step 3 one could issue this?:
>
> ./configure `pg_config —configure`

Not exactly, because pg_config emits the arguments in quotes and the
shell passes them as is to configure which doesn't like that. This
works:
eval ./configure `pg_config --configure`

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Stephen Frost 2017-12-27 14:49:51 Re: Does PostgreSQL check database integrity at startup?
Previous Message Edson Carlos Ericksson Richter 2017-12-27 12:31:53 Re: Does PostgreSQL check database integrity at startup?