| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Brown <joebrown(at)rclooke(dot)com> |
| Cc: | mha(at)sollentuna(dot)net, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #1466: #maintenace_work_mem = 16384 |
| Date: | 2005-02-08 19:52:39 |
| Message-ID: | 9577.1107892359@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Joe Brown <joebrown(at)rclooke(dot)com> writes:
> I checked all logs I could think of (event and pg_logs) and found no
> information. I suppose if I tried starting postmaster by hand I would
> have spotted the issue.
Hmm. I see at least part of the problem: the poweron default for
log_destination is "stderr" which is not very helpful on Windows;
the message is probably going to the bit bucket since any destination
change you may have requested in postgresql.conf probably hasn't been
applied yet. (Joe, if you put log_destination = eventlog in the conf
file before the mistaken entry, does it report properly?)
Seems like we need a different poweron default on Windows.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-02-09 03:35:34 | Re: BUG #1464: Borland C++ problem |
| Previous Message | Joe Brown | 2005-02-08 19:42:14 | Re: BUG #1466: #maintenace_work_mem = 16384 |