Re: deadlock with vacuum full on 7.4.5

From: Joseph Shraibman <jks(at)selectacast(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: deadlock with vacuum full on 7.4.5
Date: 2004-10-12 23:12:03
Message-ID: 416C64C3.6060605@selectacast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

That is what I wanted to know, how to get the evidence for next time.

Tom Lane wrote:
> Joseph Shraibman <jks(at)selectacast(dot)net> writes:
>
>>Why then when I did a kill -INT on the vacuuming backends did everything
>>unfreeze?
>
>
> You could have had other stuff backed up behind the VACUUM FULL lock
> requests.
>
> It's not impossible that you had a deadlock *outside* the database,
> that is some wait loop that is partially within and partially outside
> the DB. But if you want me to believe there's a bug in our deadlock
> detector, you're going to have to offer some actual evidence...
>
> regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Neumann Péter 2004-10-12 23:15:28 Return resultset from a function
Previous Message Tom Lane 2004-10-12 23:05:46 Re: deadlock with vacuum full on 7.4.5