Dave,
For the reasons you mention for using pg_ctl -w, it seemed to me the wisest option to recreate the postgres database.
Afterthe normal startup messages, the following error appears once in the log:
127.0.0.1 postgres postgres FATAL: the database system is starting up
I assume that this is due to the -w option. The service is now working normally.
Tanks,
Walter Roeland
-----Mensaje original-----
De: Dave Page [mailto:dpage@postgresql.org]
Enviado el: Miércoles, 19 de Septiembre de 2007 03:01
Para: Walter Roeland
CC: pgsql-general@postgresql.org
Asunto: Re: [GENERAL] Version 8.2.5 for Windows doesn't startup normallyafter upgrading from 8.2.4
On Tue, 2007-09-18 at 14:58 -0500, Walter Roeland wrote:
> 2007-09-18 14:28:36 127.0.0.1 postgres postgres FATAL: database
> "postgres" does not exist
>
> And I have to abort the startup.
>
> Maybe the next is a hint:
> When I had blocked the access to localhost with SSL=ON (using hostnossl
> pg_hba.conf) there was a constant complaint (2 times per second) with:
> 127.0.0.1 postgres postgres FATAL: no pg_hba.conf entry for host
> "127.0.0.1", user "postgres", database "postgres", SSL on
>
> ---------
> Have I something wrong with the configuration of the service?
Prior to 8.2.5, the -w option for pg_ctl was broken which meant that the
server would report itself running to the service control manager when
in actual fact it was still starting up. This would mean that dependent
services such as Slony or pgAgent would fail to start because the server
wasn't necessarily accepting connections at that time.
The -w option tells pg_ctl to attempt to connect to the server every few
seconds until successful - and only then report running status to the
service control manager, which will then attempt to start the dependent
services.
In your case, it seems like the 'postgres' database has been removed
which prevents pg_ctl connecting. When you blocked access through
pg_hba.conf, the fact that the database didn't exist was masked by the
lack of access to even attempt the connection.
To fix this, either:
- Modify the registry key (having taken a backup first of course) with
the pg_ctl command line, removing the -w option.
- Recreate the postgres database, and ensure it's accessible.
Regards, Dave.