TODO has:
o %Allow commenting of variables in postgresql.conf to restore them
to defaults
Currently, if a variable is commented out, it keeps the
previous uncommented value until a server restarted.
On Sun, Feb 05, 2006 at 09:56:17PM +0100, Peter Eisentraut wrote:
> > inetd, Apache, squid, exim, postfix, a famous database starting with
> > m...
>
> cron, syslog, ntp, ssh
All of those work either by re-execing themselves, if they implement a
reload at all. Except mysql which only appears to a
Joachim Wieland wrote:
> > > - other unix daemons reset their values to defaults before
> > > reading conffiles
> >
> > Examples please?
>
> inetd, Apache, squid, exim, postfix, a famous database starting with
> m...
cron, syslog, ntp, ssh
--
Peter Eisentraut
http://developer.postgresql.org/~pe
On Sun, Feb 05, 2006 at 02:37:53PM -0500, Tom Lane wrote:
> Joachim Wieland <[EMAIL PROTECTED]> writes:
> >> There's been various discussions in the past about making this behavior
> >> less non-intuitive, but nothing's been settled on ...
> > So what about deciding now that it should be changed.
On Sun, Feb 05, 2006 at 07:59:06PM +0100, Martijn van Oosterhout wrote:
> On Sun, Feb 05, 2006 at 07:43:47PM +0100, Joachim Wieland wrote:
> > I propose to change it on the grounds that:
> > - other unix daemons reset their values to defaults before reading
> >conffiles
> But the biggest iss
Joachim Wieland <[EMAIL PROTECTED]> writes:
>> There's been various discussions in the past about making this behavior
>> less non-intuitive, but nothing's been settled on ...
> So what about deciding now that it should be changed. What are the reasons
> for why it should be kept as it is?
1. Bac
On Sun, Feb 05, 2006 at 07:43:47PM +0100, Joachim Wieland wrote:
> I propose to change it on the grounds that:
>
> - other unix daemons reset their values to defaults before reading
>conffiles
To be fair, most daemons can do this by simply re-execing themselves,
something we don't have the l
On Fri, Feb 03, 2006 at 12:13:15AM -0500, Tom Lane wrote:
> I think you're getting bit by a standard beginner gotcha: commenting out
> an entry in postgresql.conf will not change the state of a running
> postmaster. (A comment is a no-op, eh?) You need to put in a
> non-comment entry that sets th
Tom Lane wrote:
I think you're getting bit by a standard beginner gotcha: commenting out
an entry in postgresql.conf will not change the state of a running
postmaster. (A comment is a no-op, eh?) You need to put in a
non-comment entry that sets the desired state.
This was indeed the case. I
Mott Leroy <[EMAIL PROTECTED]> writes:
> I turned on statement logging (and duration), issued a "pg_ctl reload"
> and got it working (logging to sys log and standard out). Now however,
> when i try to turn it off, it won't turn off, using the same procedure.
> I've now commented out all the line
On Thu, Feb 02, 2006 at 06:19:53PM -0500, Mott Leroy wrote:
> On Postgres 7.4.1
That's pretty old. If you can't upgrade to 8.0 or 8.1 then at least
consider staying up to date with bug fixes by using the latest
version in the 7.4 branch (currently 7.4.11).
> I've been experiencing some strangene
On Postgres 7.4.1
I've been experiencing some strangeness with the logging settings in
postgresql.conf.
I turned on statement logging (and duration), issued a "pg_ctl reload"
and got it working (logging to sys log and standard out). Now however,
when i try to turn it off, it won't turn off,
12 matches
Mail list logo
