Re: Standalone backend doesn't read postgresql.conf

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Standalone backend doesn't read postgresql.conf
Date: 2002-10-24 02:27:53
Message-ID: 7993.1035426473@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Philip Warner 2002-10-24 02:36:20 Re: pg_dump and large files - is this a problem?
Previous Message Philip Warner 2002-10-24 02:14:35 Re: pg_dump and large files - is this a problem?