| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Johann Spies <johann(dot)spies(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Why this lock? |
| Date: | 2015-08-25 14:09:02 |
| Message-ID: | 20024.1440511742@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Johann Spies <johann(dot)spies(at)gmail(dot)com> writes:
> On 25 August 2015 at 15:52, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> creating and index requires exclusive access. did you try the
>> concurrent variant?
> Yes. The one which I stopped after 5 days, was running concurrently. There
> was a similar lock involved.
That lock type is used by CREATE INDEX CONCURRENTLY when it has to wait
out another transaction. There is no way around this, it's an inherent
part of that algorithm.
http://www.postgresql.org/docs/9.4/static/sql-createindex.html#SQL-CREATEINDEX-CONCURRENTLY
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2015-08-25 14:17:09 | Re: PostgreSQL Developer Best Practices |
| Previous Message | Johann Spies | 2015-08-25 13:54:53 | Re: Why this lock? |