Re: Concurrent VACUUM and ANALYZE - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: Concurrent VACUUM and ANALYZE
Date
Msg-id 36e682920807211829i4775e91cx132ce809e074e3d5@mail.gmail.com
Whole thread Raw
In response to Re: Concurrent VACUUM and ANALYZE  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
On Mon, Jul 21, 2008 at 6:15 PM, Alvaro Herrera
<alvherre@commandprompt.com> wrote:
> This means that VACUUM ANALYZE must grab both locks ... is there a
> gotcha here?

Agreed.

> The main problem I see with this idea is that the dead and total tuple
> count computed by ANALYZE would be immediately out of date, and if it
> happens to finish after VACUUM then it'll overwrite the values the
> latter just wrote, which are more correct.  Not sure how serious a
> problem this is.

Agreed, but in the worst case, it's no different than running ANALYZE
immediately following a VACUUM.

-Jonah


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Concurrent VACUUM and ANALYZE
Next
From: Tom Lane
Date:
Subject: Re: [patch] plproxy v2