| From: | Alban Hertroys <haramrae(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| 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-26 23:27:05 |
| Message-ID: | DC55854D-8BB1-44C8-9212-CF3988B8E50B@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On 26 Dec 2017, at 18:11, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-12-27 00:43:03 | Re: Deadlock between concurrent index builds on different tables |
| Previous Message | Martin Marques | 2017-12-26 22:42:58 | Re: Does PostgreSQL check database integrity at startup? |