I would go with the permissions issue. Not all postgres startup problems are logged in pg_log. Go check the Application log: right click on Computer -> Manage -> Events -> Application and look for any errors with PG as a source. It may be connected to the fact that somehow postgres user doesn't have permission to write postmaster.pid file either to delete the old one or creating new one. At least this is the main issue I came accross in our clients' DBs. If the postmaster.pid file is created check forr errors like "bogus data in postmaster.pid" as this is another thing that may be the case. 2010/10/18 Thomas Kellerer <spam_eater@xxxxxxx>: > Joe Carr wrote on 18.10.2010 23:11: >> >> Hello all, I have a windows postgres 9.0.1 installation which doesn't >> start, and also doesn't log any information. The only evidence that >> an attempt was made is in the event log with the following pair of >> messages : >> >> 1. Waiting for server startup... 2. Timed out waiting for server >> startup >> >> I've tried to run postgres.exe from the command line to glean more >> information, but it starts and stops without any output as well. > > Did you try using pg_ctl instead (e.g. copy the commandline from the service > definition)? > > In most of the cases it's a permission issue with the data directory. Did > you verify the postgres user (the one under which the service is started) > has full access to the data directory? > > Regards > Thomas > > > -- > Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) > To make changes to your subscription: > http://www.postgresql.org/mailpref/pgsql-admin > -- Åukasz Brodziak II MU Bioinformatyka -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
