Skip site navigation (1) Skip section navigation (2)

Re: CIC and deadlocks

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CIC and deadlocks
Date: 2007-03-31 15:38:30
Message-ID: 5980.1175355510@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> writes:
> Isn't CREATE INDEX CONCURRENTLY prone deadlock conditions ?

Can you give a specific example?  The deadlock code will grant locks
out-of-order in cases where the alternative is to abort somebody.
I think you may be describing a missed opportunity in that logic,
more than a reason to add still another fragile assumption for HOT.

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Joshua D. DrakeDate: 2007-03-31 15:46:03
Subject: Re: Feature thought: idle in transaction timeout
Previous:From: korrydDate: 2007-03-31 13:34:16
Subject: Re: Last minute mini-proposal (I know, I know) forPQexecf()

pgsql-patches by date

Next:From: Tom LaneDate: 2007-03-31 15:51:20
Subject: Re: COPY-able sql log outputs
Previous:From: Magnus HaganderDate: 2007-03-31 14:09:18
Subject: Re: COPY-able sql log outputs

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group