| From: | Oliver Kohll - Mailing Lists <oliver(dot)lists(at)gtwm(dot)co(dot)uk> |
|---|---|
| To: | "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
| Cc: | "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Index creation problem |
| Date: | 2012-10-19 15:06:17 |
| Message-ID: | A655178E-E20C-41FD-B4C6-B11AD3E03286@gtwm.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 19 Oct 2012, at 15:09, "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at> wrote:
> You should always include the list in your replies -
> other people might be interested in the solution.
Oops, thought I had.
>
> There must be at least two transactions involved
> to create a locking problem like you describe.
> But since CREATE INDEX takes strong locks, it can
> easily get locked by other "harmless" things.
OK, I've reduced the calls to CREATE INDEX, waiting to test that. If there's still an issue I will use CONCURRENTLY as you suggested.
Many thanks
Oliver
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shaun Thomas | 2012-10-19 16:01:33 | Re: Multiple Cluster on same host |
| Previous Message | GMAIL | 2012-10-19 14:59:24 | Re: Multiple Cluster on same host |