| From: | Andrew Sullivan <andrew(at)libertyrms(dot)info> |
|---|---|
| To: | PostgreSQL general list <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: log_timestamp and SIGHUP? |
| Date: | 2003-03-20 13:29:05 |
| Message-ID: | 20030320082905.B15063@mail.libertyrms.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(at)libertyrms(dot)info> M2P 2A8
+1 416 646 3304 x110
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Liu, Mingyi | 2003-03-20 14:05:24 | transaction problem (delete/select/insert sequence fails, a bug?) |
| Previous Message | Miguel Carvalho | 2003-03-20 12:55:05 | Re: Trigger issue, bug? on 7.2.1 |