From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matt Bartolome <mattxbart(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgres startup failure |
Date: | 2010-05-21 13:40:07 |
Message-ID: | 18729.1274449207@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Matt Bartolome <mattxbart(at)gmail(dot)com> writes:
> On Thu, May 20, 2010 at 3:36 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> So right now I'm wondering whether you're not failing to notice
>> a relevant log message(s). You've evidently managed to launch
>> the syslogger --- where is it configured to write the postmaster
>> log?
> Gosh, you know I never even bothered looking in pg_log. Stupid! I was
> expecting to see some sort of error when doing:
> $ postgres -d 3 -D /data/postgres/
I wonder whether it'd be a good idea to write a log message on the order
of "switching to syslogger" just before cutting over the log output
during startup. That's probably not quite the best wording, but
something like that might help to remind people where to look.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | christophe.andre | 2010-05-21 13:43:30 | Is postgres installed? |
Previous Message | Chris Smith | 2010-05-21 13:31:40 | Re: How feasible is this? |