Re: Error that shouldn't happen?

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: Rob Brucks <rob(dot)brucks(at)rackspace(dot)com>
Cc: "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Error that shouldn't happen?
Date: 2017-05-18 20:05:15
Message-ID: CAKFQuwbDnNxzK59FcL=nvt45vfLsOzOiVLeqka-RHig2Rn1s7w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 18, 2017 at 12:48 PM, Rob Brucks <rob(dot)brucks(at)rackspace(dot)com>
wrote:

> I am unable to figure out how the trigger was able to successfully create
> the table, but then fail creating the index. I would have expected one
> thread to "win" and create both the table and index, but other threads
> would fail when creating the table… but NOT when creating the index.
>

​I don't fully comprehend the locking involved here but if you want a
failure while creating the table you shouldn't use "IF NOT EXISTS". ​On
the other side adding "IF NOT EXISTS" to the CREATE INDEX will supposedly
prevent the error you are seeing.

The trigger that failed to create the index also failed to create the table
- it just didn't care because of the IF NOT EXISTS. At least this is what
I am observing from your description.

David J.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Rob Brucks 2017-05-18 20:18:36 Re: Error that shouldn't happen?
Previous Message Rob Brucks 2017-05-18 19:48:56 Error that shouldn't happen?