w/egg on face, DOH
I did try to make sure I didn't submit a bogus report, but didn't try hard enough.
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.
This didn't help me diagnose the issue:
runas /user:postgres "p:\PostgreSQL\8.0\bin\pg_ctl.exe start -D p:\PostgreSQL\8.0\data"
Ok, now I ask for the world... Can we force postgres to log startup failure? I figured that was what was going on, but I didn't think to login as postgres and start it by hand to see the output.
Tom Lane wrote:
"Joe Brown" <[EMAIL PROTECTED]> writes:
Uncommenting maintenace_work_mem = 16384
caused the server immediately stop after start.
You apparently managed to change the spelling while uncommenting; the actual line in the sample file is
#maintenance_work_mem = 16384 # min 1024, size in KB ^
No errors reported, no logs generated.
The error is reported. For instance, when I try this I get $ postmaster FATAL: unrecognized configuration parameter "maintenace_work_mem" $
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
