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

Add to TODO:

    * Exit postmaster if postgresql.conf can not be opened


---------------------------------------------------------------------------

Robert Treat wrote:
> 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
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073