On Mon, Oct 14, 2013 at 6:31 AM, Florian Nigsch <flo@nigsch.eu> wrote:
My question is then - where does this error come from? Is is because Postgres allocates the same name (table1_lower_idx) twice when the index begins building, because at that time there's no index present with that name? But if one index finishes earlier, then the second one can't be committed because it has the same name as an already present index?
looks like the auto-generated names for your indexes clash. Give them explicit names.
Also, subscribe to the list if you want help. this is not your private help desk.