> -----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
> I have read about pg_ctlcluster in the net they are saying this below
> pg_ctlcluste With the --force option the "fast" mode is used which
> back all active transactions, disconnects clients immediately and thus
> down cleanly. If that does not work, shutdown is attempted again in
> "immediate" mode, which can leave the cluster in an inconsistent state
> 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.
In response to
pgsql-admin by date
|Next:||From: Nicholson, Brad (Toronto, ON, CA)||Date: 2011-03-22 14:13:05|
|Subject: Re: Memory limits and PostgreSQL 8.4 - Over 63 GB of memory
|Previous:||From: Bill Teluk||Date: 2011-03-22 03:56:27|
|Subject: Re: psql causing a error|