Hello Markus,
Thanks for the reply.
For the past one week postgreSQL service has been running absolutely fine -:)
Also there is no OOM killer application on the windows 2003 server. I haven't made any changes on the machine since first the service failed.
Nothing in the event logs also.
Can there be any another reason why the service failed ?
--
Thanks and Regards
Bhaskar Sirohi
bhaskar.sirohi@druvaa.com
www.druvaa.com
(C) +91 986 094 6619
Thanks for the reply.
For the past one week postgreSQL service has been running absolutely fine -:)
Also there is no OOM killer application on the windows 2003 server. I haven't made any changes on the machine since first the service failed.
Nothing in the event logs also.
Can there be any another reason why the service failed ?
--
Thanks and Regards
Bhaskar Sirohi
bhaskar.sirohi@druvaa.com
www.druvaa.com
(C) +91 986 094 6619
On Tue, Aug 5, 2008 at 5:50 PM, Markus Wanner <markus@bluegap.ch> wrote:
Hi,
Bhaskar Sirohi wrote:
> ...These log lines look like your database is touching lots of tuples, requiring it to checkpoint frequently. Then it receives a fast shutdown request - from whoever.
2008-07-30 15:05:01 EDT LOG: checkpoints are occurring too frequently (28
seconds apart)
2008-07-30 15:05:01 EDT HINT: Consider increasing the configuration
parameter "checkpoint_segments".
2008-07-30 15:13:34 EDT LOG: checkpoints are occurring too frequently (29
seconds apart)
2008-07-30 15:13:34 EDT HINT: Consider increasing the configuration
parameter "checkpoint_segments".
2008-07-30 15:18:50 EDT LOG: checkpoints are occurring too frequently (28
seconds apart)
2008-07-30 15:18:50 EDT HINT: Consider increasing the configuration
parameter "checkpoint_segments".
2008-07-30 15:19:21 EDT LOG: received fast shutdown request
What causes the workload? Did you check memory usage? (And uh.. does Windows 2003 Server have an OOM Killer or some such?)
Regards
Markus Wanner
No comments:
Post a Comment