Re: pg_stat_all_tables column value reseting problem. - Mailing list pgsql-admin

From Nicholson, Brad (Toronto, ON, CA)
Subject Re: pg_stat_all_tables column value reseting problem.
Date
Msg-id 2626AEE4839D064CB0472A3814DC403F46D211B57F@GVW1092EXB.americas.hpqcorp.net
Whole thread Raw
In response to Re: pg_stat_all_tables column value reseting problem.  (leslie samuel <leslie.bks@gmail.com>)
List pgsql-admin
> -----Original Message-----
> From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-
> owner@postgresql.org] On Behalf Of leslie samuel
> Sent: Saturday, March 19, 2011 8:49 AM
> To: pgsql-admin@postgresql.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.


pgsql-admin by date:

Previous
From: Robert Treat
Date:
Subject: Re: Backup hot-standby database.
Next
From: "Nicholson, Brad (Toronto, ON, CA)"
Date:
Subject: Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory for DB?