From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ravi Kapoor <ravikapoor101(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: questions about 2nd index on one column |
Date: | 2017-01-03 19:26:12 |
Message-ID: | 8087abd0-6c4a-37f2-2e22-f94e4e3ffb55@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 01/03/2017 11:07 AM, Ravi Kapoor wrote:
>
> I have a bit strange question. I am trying to figure out how to avoid
> table locking while creating an index through Django (1.5.1) in Postgres
> 9.4.7
>
> Django 1.5.1 does not support concurrent indexing. So my thought is to
> first create a concurrent index using SQL prompt.
> Then try to update django model to add index, which will effectively
> create 2 indexes on same column.
I really need to read the entire subject. So in response to my own
question, yes it is on one column.
>
> So my questions are:
>
> If I create a 2nd index on one column,
> 1. Does postgres scan entire table to create index from scratch or does
> it simply copy the first index?
> 2. Does postgres lock the table to create this index?
>
> thanks
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2017-01-03 20:09:08 | Re: questions about 2nd index on one column |
Previous Message | Adrian Klaver | 2017-01-03 19:24:12 | Re: questions about 2nd index on one column |