| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Subhasis Bhattacharya <subhasis(dot)bhattacharya(at)gmail(dot)com> |
| Cc: | Craig Ringer <craig(at)2ndquadrant(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Autovaccum failure with Postgres 8.3.14? (max-fsm_pages issue?) |
| Date: | 2012-11-27 23:25:40 |
| Message-ID: | CAOR=d=0y2N00GVvjHaPnmeTdb1fu+nZpYTr5ZkC4K=b165R7Bg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Sat, Nov 24, 2012 at 7:25 AM, Subhasis Bhattacharya
<subhasis(dot)bhattacharya(at)gmail(dot)com> wrote:
> Thanks Craig,
>
> We have plans to upgrade to a later version of postgres, but that could take
> a while.
>
> Meantime, I wanted to understand whether the autovacuum failure could be
> linked to the fact that the stats collector could not update (rename) the
> pgstats file?
It's important to understand that Craig is implying you're getting
bitten by a bug in an early version of pg 8.3 that can be fixed by
updating to a later version of pg 8.3. Updating within a minor
version number like that causes minimum down time as it simply copies
in new binary files and restarts the db with no need for upgrading the
/data directory. On most debian based boxes it's as simple as:
sudo apt-get update
or
sudo apt-get upgrade
| From | Date | Subject | |
|---|---|---|---|
| Next Message | subhasis.bhattacharya | 2012-11-28 05:05:16 | Re: Autovaccum failure with Postgres 8.3.14? (max-fsm_pages issue?) |
| Previous Message | Victor Rosenberg | 2012-11-27 15:34:25 | Changing logging options for PostgreSQL service on windows |