From: | Tony Webb <amw(at)sanger(dot)ac(dot)uk> |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | pg_ctlcluster not logging error (memory problem likely) |
Date: | 2009-03-26 09:26:13 |
Message-ID: | 49CB4A35.1030002@sanger.ac.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Hi,
I'm trying to find out why my cluster won't start. It looks like I'm
pushing up max_connections too high although I think my memory and
semaphore settings are OK. Thing is, when the cluster fails to start I
can't see any errors in pg_log or in /var/log/messages.
When the cluster is up and running it seems to write normally to these
locations.
Could pg_ctlcluster be writing somewhere else? can I do something to see
more verbose messages (more than the empty string) other than setting
log parameters in postgres.conf?
I'm running 8.3 on Debian btw.
Cheers
Pif
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2009-03-26 09:44:34 | Re: [ADMIN] Can we load all database objects in memory? |
Previous Message | Scott Marlowe | 2009-03-25 20:12:25 | Re: [SQL] Can we load all database objects in memory? |