Re: Deadlock while doing VACUUM??

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Brown <kevin(at)sysexperts(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Deadlock while doing VACUUM??
Date: 2003-03-27 14:29:10
Message-ID: 11237.1048775350@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> When a heavy INSERT or UPDATE load on a table is occurring (lots of
> quick INSERTs or UPDATEs within a single transaction), a VACUUM
> ANALYZE (or just straight VACUUM) has a really good chance (10% or so)
> of causing either the INSERT/UPDATE or the VACUUM to fail with a
> "deadlock detected" error.

I was unable to replicate this in CVS tip, using "pgbench -c 10 -t 1000"
as the load generator.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Meskes 2003-03-27 14:43:58 Re: pgtypeslib/timestamp problem
Previous Message Tom Lane 2003-03-27 14:07:48 Re: pgtypeslib/timestamp problem