Gregory Stark wrote:
> "Alvaro Herrera" <alvherre(at)commandprompt(dot)com> writes:
>> Hmm, it looks like the race condition Heikki mentioned is the culprit.
>> We need a way to stop future analyzes from starting. Back to the
>> drawing board ...
> A crazy idea I just had -- what if you roll this into the deadlock check? So
> after waiting on the lock for 1s it wakes up, finds that the holder it's
> waiting on is an autovacuum process and cancels it instead of finding no
Another idea would be to make no changes to the relation_openrv call,
but have autovacuum periodically check if anyone's blocked waiting on
its locks, and commit suicide (or set cost delay to zero) if so.
In response to
pgsql-hackers by date
|Next:||From: Pavel Stehule||Date: 2007-10-04 15:52:50|
|Subject: tsearch2 wrapper|
|Previous:||From: Josh Berkus||Date: 2007-10-04 15:43:24|
|Subject: Re: What does 'elapsed' exact means in PostgreSQL Log Statistics|