Re: log_timestamp and SIGHUP? - Mailing list pgsql-general

From Andrew Sullivan
Subject Re: log_timestamp and SIGHUP?
Date
Msg-id 20030320082905.B15063@mail.libertyrms.com
Whole thread Raw
In response to Re: log_timestamp and SIGHUP?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: log_timestamp and SIGHUP?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Tue, Mar 18, 2003 at 11:47:23PM -0500, Tom Lane wrote:
> It sure looks like it should, modulo the fact that backends won't
> re-read postgresql.conf until they next reach the
> wait-for-client-command outer loop.

Hmm.  The outer loop should surely happen after a COMMIT/ROLLBACK,
right?

> You sure you SIGHUP'd the right process?

Well, assuming the postmaster.pid file wasn't lying.  But yes,
because some of the other changes I made did take effect.

A

--
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110


pgsql-general by date:

Previous
From: "Daniel R. Anderson"
Date:
Subject: Re: PostgreSQL downloads compressed with bzip2 instead of
Next
From: "Liu, Mingyi"
Date:
Subject: transaction problem (delete/select/insert sequence fails, a bug?)