Re: BUG #1331: after update: vacuum blocks parallel to select

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Enke, Michael" <michael(dot)enke(at)wincor-nixdorf(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1331: after update: vacuum blocks parallel to select
Date: 2004-11-29 16:27:14
Message-ID: 19023.1101745634@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"Enke, Michael" <michael(dot)enke(at)wincor-nixdorf(dot)com> writes:
> But the description says: vacuum can run parallel to selects.
> This is than not true.

Sure it can; but that doesn't mean there is no interlocking at all.

The issue you have is not so much that the select is running as that it
is *not* running, ie, it's stopped on a particular page. As soon as it
moves off the modified page, the vacuum will be able to make progress.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-11-29 16:59:28 Re: BUG #1329: Bug in IF-ELSEIF-ELSE construct
Previous Message Enke, Michael 2004-11-29 16:19:20 Re: BUG #1331: after update: vacuum blocks parallel to select