> Please reply to list also.
apologies, my bad.
> It would seem that the index would not be rebuilt, assuming all
conditions are the same.
Thanks for finding this. This is enough info for me to spend a day
experimenting. I did not want to waste a day if we knew upfront that it
wont work. But looks
On 01/03/2017 11:35 AM, Ravi Kapoor wrote:
Please reply to list also.
Ccing list.
> Yes I am aware of django EOL. However, our company is still using it, we
> have a migration plan later this year, however for now, I got to work
> with what we have.
Still, you are missing 14 patch releases to the
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
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
First Django 1.5.x has been past end of life for 2.25 years.
Second before it went EOL it was up to 1.
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 mo
