From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
---|---|
To: | "sthomas(at)optionshouse(dot)com" <sthomas(at)optionshouse(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Something Weird Going on with VACUUM ANALYZE |
Date: | 2013-09-18 16:50:22 |
Message-ID: | CAMkU=1zxhPBr5-QXjZ54UuH7YvrkqddtAe6FkyWk31sP+kV4Vw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 17, 2013 at 1:39 PM, Shaun Thomas <sthomas(at)optionshouse(dot)com>wrote:
> Hey,
>
> This is PostgreSQL 9.1.9.
>
>
...
> Apparently something magical happened last Friday, and now analyze is
> broken somehow? Am I missing something, here? The log claims everything
> worked out OK:
>
> 2013-09-17 03:20:37 CDT|STATEMENT: VACUUM (VERBOSE, ANALYZE);
> 2013-09-17 03:37:31 CDT|LOG: duration: 2246467.567 ms statement: VACUUM
> (VERBOSE, ANALYZE);
>
> These are from the same pid doing the vacuum. What's weird, is that the
> lines don't match up in time. The reported duration is 37 minutes, and
> since the vacuum launches at 3:00am, it matches with the last line. If
> that's the case, what on Earth is that line at 3:20 all about?
That line is the final line of a multi-line log entry. To know what it is
about, you need to look at the lines before it in the logfile. Perhaps it
is failing to obtain a lock or something.
Cheers,
Jeff
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2013-09-18 17:25:20 | Re: Query - CPU issue |
Previous Message | Gabriel E. Sánchez Martínez | 2013-09-18 16:36:03 | Re: nested partitioning |