| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: autovacuum and immediate shutdown issues |
| Date: | 2009-10-19 17:27:34 |
| Message-ID: | 7946.1255973254@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
> All of this is completely besides the point that a database that's
> been shutdown immediately / had the power cord yanked comes back up
> and doesn't start autovacuuming automatically, which seems a
> non-optimal behaviour.
It'll start as soon as you've modified enough rows. The absolute worst
case behavior is that table bloat reaches twice the level it would have
otherwise, or pg_statistic data becomes twice as out of date as it would
have otherwise.
Now, if your server's MTBF is less than the autovac interval, you could
indeed have an accumulating problem ... but I suggest that in that
situation you've got other issues to fix.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerhard Wiesinger | 2009-10-19 17:49:20 | Re: Function returning 2 columns evaluated twice when both columns are needed |
| Previous Message | Brad Nicholson | 2009-10-19 17:25:05 | Re: autovacuum and immediate shutdown issues |