"stats_start_collector" is an obsolete parameter in 8.3, that's why PG
wouldn't start with it.
Igor
-----Original Message-----
From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of bogdad
Sent: Wednesday, July 02, 2008 2:38 PM
To: pgsql-admin@postgresql.org
Subject: [ADMIN] Postgres windows service shutdowns after start
Hi,
I have a postgres 8.3 service working on win2003 server, it works fine.
But, when i alter postgresql.conf adding the stats_starts_collector = on
( or even false, which bugs me to the end) the service starts and
immedeately stops. If I revert the change, service works again.
The event log is clear, the pg_log is empty.
My login is local admin, and due to restrictions in environment, i
currently cannot runas /user:postgres posmaster.exe to retrieve the
stderr or stdout of postgres.
So the questions:
1) Is it really connected to stats collector? [ the part in brackets
makes me think it's not]
2) Maybe, there is a forsaken way for admin user to run postgres?
3) How to proceed?
4) Is there a way to syntax check .conf?
(I know that I can send the .conf home and run postgres there, but don't
like this option)
Thanks in advance,
Vladimir.
--
View this message in context:
http://www.nabble.com/Postgres-windows-service-shutdowns-after-start-tp1
8244024p18244024.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
