pg_ctlcluster not logging error (memory problem likely) - Mailing list pgsql-admin

From Tony Webb
Subject pg_ctlcluster not logging error (memory problem likely)
Date
Msg-id 49CB4A35.1030002@sanger.ac.uk
Whole thread Raw
Responses Re: pg_ctlcluster not logging error (memory problem likely)
List 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.

pgsql-admin by date:

Previous
From: Iñigo Martinez Lasala
Date:
Subject: Re: [SQL] Can we load all database objects in memory?
Next
From: "Sabin Coanda"
Date:
Subject: plain text difference with pg_dump