Received: from localhost (maia-1.hub.org [200.46.204.191]) by postgresql.org (Postfix) with ESMTP id 759B39F9B05; Tue, 26 Dec 2006 10:21:58 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.191]) (amavisd-new, port 10024) with ESMTP id 21327-08; Tue, 26 Dec 2006 10:21:48 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 X-Greylist: from auto-whitelisted by SQLgrey-1.7.4 Received: from perth.mailnetwork.co.uk (perth.mailnetwork.co.uk [80.175.28.46]) by postgresql.org (Postfix) with ESMTP id 451019F939F; Tue, 26 Dec 2006 10:21:49 -0400 (AST) Received: from user-514f7b79.l4.c3.dsl.pol.co.uk ([81.79.123.121]:1251 helo=[192.168.1.2]) by perth.mailnetwork.co.uk with esmtpa (Exim 4.63) (envelope-from ) id 1GzDBc-0000Yp-Iy; Tue, 26 Dec 2006 14:21:48 +0000 Message-ID: <45913054.8080806@mailnetwork.co.uk> Date: Tue, 26 Dec 2006 14:23:16 +0000 From: "Andy Shellam (Mailing Lists)" User-Agent: Thunderbird 1.5.0.9 (Windows/20061207) MIME-Version: 1.0 To: vinayakr@vmoksha.com CC: pgsql-admin@postgresql.org, pgadmin-support@postgresql.org Subject: Re: [ADMIN] DB problem References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200612/139 X-Sequence-Number: 6406 Vinayak, Please don't post twice to two different lists (four of the same posts to both pgsql-admin and pgadmin-support.) This clearly isn't a problem with PG Admin - so don't clutter that list up, and don't multiple-post - it won't change anything posting twice, and if anything you'll only end up annoying people so they won't feel obliged to help you anyway. In answer to your question, it took me 3 minutes to find this manual page: http://www.postgresql.org/docs/7.3/static/runtime-config.html There is no log_directory setting, but it is in 8.x (http://www.postgresql.org/docs/8.0/static/runtime-config.html), so your version doesn't support it. It would be helpful if you consult the manual for your running version, not the current release, as features inevitably get added and others change. And, as someone's already said, you should be thinking of upgrading to at minimum 8.1. Andy. vinayakr@vmoksha.com wrote: > Hi, > > We are using PostgreSQL 7.3 version, installed in linux system. Only > DB is getting shut down 3-4 times a day. From my application end I get > "Sorry too many clients" error. > Refering the FAQ I maximized the DB session limit to 200. > > I think the logs are not enabled in my DB. So I set the following > options in postgresql.con file > > log_timestamp= true > log_directory=pg_log > log_filename=%Y-%m-%d_%H%M%S.log > log_disconnections=true > log_hostname=true > log_statement=true > > > After restarting the system got the following error : > [root@localhost root]# su postgres bash-2.05b$ postmaster -i -D > /var/lib/pgsql/data FATAL: postgresql.conf:131: syntax error, > token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: > postgresql.conf:131: syntax error, token="%" bash-2.05b$ postmaster -i > -D /var/lib/pgsql/data FATAL: postgresql.conf:131: syntax error, > token="%" bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: > 'log_directory' is not a valid option name bash-2.05b$ postmaster -i > -D /var/lib/pgsql/data FATAL: 'log_directory' is not a valid option > name bash-2.05b$ postmaster -i -D /var/lib/pgsql/data FATAL: > 'log_filename' is not a valid option name bash-2.05b$ postmaster -i -D > /var/lib/pgsql/data FATAL: 'log_disconnections' is not a valid option > name bash-2.05b$ postmaster -i -D /var/lib/pg > > When you install the DB, the logs are enabled by default? > > Would you pls tell me still what setting need to be done? > > Thanks, > Vinayak V. Raikar > Extn : 143 > > !DSPAM:37,4590b56931941914011633! -- Andy Shellam NetServe Support Team the Mail Network "an alternative in a standardised world" p: +44 (0) 121 288 0832/0839 m: +44 (0) 7818 000834