Re: Problem with tcp/ip connection, postgresql.conf

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Problem with tcp/ip connection, postgresql.conf
Date: 2003-06-09 15:38:26
Message-ID: 1055173106.29944.393.camel@camel
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

On Sun, 2003-06-08 at 11:50, Tom Lane wrote:
>
> While experimenting with this, I noted that the postmaster will not
> complain if postgresql.conf is not found --- though it will complain if
> it finds the file but can't read it (eg permission failures). It seems
> to me this is a bug, or at any rate a bad idea. There should be at least
> a warning message if the postgresql.conf file isn't found, and quite
> possibly the postmaster should refuse to start at all, on the grounds
> that you may have pointed it to a a bogus data directory.
>
> Any opinions about this out there?
>

IIRC this was going to be addressed in the "option to put config files
anywhere" patch. if not it should at least issue a warning. I'd
actually be in favor of explicit error/refusal to start if it didn't
seem so draconian.

Robert Treat
--
Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jonathan Gardner 2003-06-09 16:55:52 Re: unsubscribe
Previous Message Robert Treat 2003-06-09 15:10:34 Re: White Paper