Thanks, Tom, I messed it up myself, see my other post.
Am 04.06.2012 um 01:16 schrieb Tom Lane:
> Alexander Reichstadt writes:
>>> So sure enough that process claimed to might be starting does not end up
>>> being a process. Where do I look for what's actually going on?
>
> In the postmaster l
I found the issue, I changed the connection amount. I changed it back now.
Alex
Am 04.06.2012 um 00:39 schrieb Alexander Reichstadt:
> Hi,
>
> how do I troubleshoot postgres? It simply won't start any more. I cannot
> login, not locally nor remotely. I tried a couple of things without success.
Alexander Reichstadt writes:
>> So sure enough that process claimed to might be starting does not end up
>> being a process. Where do I look for what's actually going on?
In the postmaster log ...
>> This is the log output:
>> 04.06.12 00:26:29,792 com.edb.launchd.postgresql-9.1:If the
Btw, this is OSX 10.7.
Am 04.06.2012 um 00:39 schrieb Alexander Reichstadt:
> Hi,
>
> how do I troubleshoot postgres? It simply won't start any more. I cannot
> login, not locally nor remotely. I tried a couple of things without success.
>
> bash-3.2$ ps -Ac | egrep postgres
> bash-3.2$ /Libr
Hi,
how do I troubleshoot postgres? It simply won't start any more. I cannot login,
not locally nor remotely. I tried a couple of things without success.
bash-3.2$ ps -Ac | egrep postgres
bash-3.2$ /Library/PostgreSQL/9.1/bin/pg_ctl start -D
/Library/PostgreSQL/9.1/data -l postgres.log
pg_ctl:
