From: | "Jeremy Haile" <jhaile(at)fastmail(dot)fm> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Matthew T(dot) O'Connor" <matthew(at)zeut(dot)net>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: Autoanalyze settings with zero scale factor |
Date: | 2007-01-18 21:53:21 |
Message-ID: | 1169157201.18501.1169996967@webmail.messagingengine.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Well - it hadn't run on any table in over 24 hours (according to
pg_stat_user_tables). My tables are constantly being inserted into and
deleted from, and the autovacuum settings are pretty aggressive. I also
had not seen the autovac process running in the past 24 hours. (although
I wasn't watching it *all* the time)
So - as far as I could tell it wasn't running.
On Thu, 18 Jan 2007 16:30:17 -0500, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> said:
> "Jeremy Haile" <jhaile(at)fastmail(dot)fm> writes:
> > No tables have been vacuumed or analyzed today. I had thought that this
> > problem was due to my pg_autovacuum changes, but perhaps not. I
> > restarted PostgreSQL (in production - yikes) About a minute after being
> > restarted, the autovac process fired up.
>
> > What could get PG in a state where autovac isn't running?
>
> Um, are you sure it wasn't? The autovac process is not an always-there
> thing, it quits after each pass and then the postmaster starts a new one
> awhile later.
>
> regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-01-18 22:11:37 | Re: Configuration Advice |
Previous Message | Tom Lane | 2007-01-18 21:52:58 | Re: [PERFORM] Postgres and really huge tables |