From: | "Nicholson, Brad (Toronto, ON, CA)" <bnicholson(at)hp(dot)com> |
---|---|
To: | leslie samuel <leslie(dot)bks(at)gmail(dot)com>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_stat_all_tables column value reseting problem. |
Date: | 2011-03-22 13:57:48 |
Message-ID: | 2626AEE4839D064CB0472A3814DC403F46D211B57F@GVW1092EXB.americas.hpqcorp.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> -----Original Message-----
> From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-
> owner(at)postgresql(dot)org] On Behalf Of leslie samuel
> Sent: Saturday, March 19, 2011 8:49 AM
> To: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] pg_stat_all_tables column value reseting problem.
>
> For stop/Restart the postmaster, I am using pg_ctlcluster --force
> command.
>
> I have read about pg_ctlcluster in the net they are saying this below
> things,
>
> pg_ctlcluste With the --force option the "fast" mode is used which
> rolls
> back all active transactions, disconnects clients immediately and thus
> shuts
> down cleanly. If that does not work, shutdown is attempted again in
> "immediate" mode, which can leave the cluster in an inconsistent state
> and
> thus will lead to a recovery run at the next start.
Check your DB logs. If you are going through recovery on startup, that is your answer.
Brad.
From | Date | Subject | |
---|---|---|---|
Next Message | Nicholson, Brad (Toronto, ON, CA) | 2011-03-22 14:13:05 | Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB? |
Previous Message | Bill Teluk | 2011-03-22 03:56:27 | Re: psql causing a error |