From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | hba load error and silent mode |
Date: | 2009-08-24 12:39:02 |
Message-ID: | 4A9289E6.4050606@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Last night I had to deal with a puzzled user of version 8.4 who found
postgres refused to start but didn't log any error. It turned out that
there was an error in the pg_hba.conf file, and the client was running
in silent mode (the SUSE default).
This seems like a bug, and it's certainly not very postgres-like behaviour.
Can we move the call to hba_load() in postmaster.c down a bit so it
occurs after the SysLogger is set up? ISTM we really need an absolute
minimum of code between the call to pmdaemonize() and SysLogger_Start().
(Maybe there's a good case for deprecating silent mode. I'm not sure why
Suse uses it. Other distros don't seem to feel the need.)
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2009-08-24 12:57:02 | Re: hba load error and silent mode |
Previous Message | Zdenek Kotala | 2009-08-24 12:36:27 | Re: SIGUSR1 pingpong between master na autovacum launcher causes crash |