Does anyone remember why a standalone backend doesn't read
postgresql.conf?

For example, I just set 'autocommit' to off in postgresql.conf, and
after starting the standalone backend, it doesn't have autocommit off.

-- 
  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

Wed, 23 Oct 2002 21:22:29 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Standalone backend doesn't read postgresql.conf
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> Does anyone remember why a standalone backend doesn't read
> postgresql.conf?

Hm.  I remember why it doesn't pay attention to the per-user and
per-database settings (if they're screwed up, you might have no
way to get in and fix 'em).  But that argument doesn't apply to
postgresql.conf, since you can always fix it with a text editor.

This might just be an oversight.  Peter, any comments?

			regards, tom lane

Wed, 23 Oct 2002 22:27:53 -0400
Tom Lane <tgl@sss.pgh.pa.us>
Re: Standalone backend doesn't read postgresql.conf 