Re: My Postgresql is inaccessible in Windows 8.1

On 08/03/2016 10:15 AM, melvin6925 wrote:
> If Postgresql were running, then he would have not had the problem.
> Would he?


Except the original post was about Postgres running, but having periods
of slow down/inaccessibility. There was a later log entry showing the
pid conflict. Since I am not sure how we got from A to B and what the
current status is I would be hesitant to suggest just pulling a lock
file out from under what could be a running service. The effort to check
is negligible in relation to the benefits that accrue.

>
>
>
> Sent via the Samsung Galaxy S® 6, an AT&T 4G LTE smartphone
>
> -------- Original message --------
> From: Adrian Klaver <adrian.klaver@aklaver.com>
> Date: 8/3/16 13:01 (GMT-05:00)
> To: Melvin Davidson <melvin6925@gmail.com>
> Cc: "Edson F. Lidorio" <edson@openmailbox.org>,
> pgsql-general@postgresql.org
> Subject: Re: [GENERAL] My Postgresql is inaccessible in Windows 8.1
>
> On 08/03/2016 08:47 AM, Melvin Davidson wrote:
>>
>>
>
>>
>>
>>     Well this looks like the Postgres log and it is showing that you are
>>     trying to start Postgres when there is already another instance of
>>     Postgres running.
>>
>>     What does the Task Manager show is running?
>>
>>     When I was talking about system logs I meant the OS logs, I was not
>>     clear on that point.
>>
>>
>>     --
>>     Adrian Klaver
>>     adrian.klaver@aklaver.com <mailto:adrian.klaver@aklaver.com>
>>
>>
>>
>>     --
>>     Sent via pgsql-general mailing list (pgsql-general@postgresql.org
>>     <mailto:pgsql-general@postgresql.org>)
>>     To make changes to your subscription:
>>     http://www.postgresql.org/mailpref/pgsql-general
>>
>>
>> *> 2016-08-02 17:05:59 BRT LOG:  database system was not properly shut
>>> down; automatic recovery in progress
>>
>> <2016-08-03 08:42:39 BRT FATAL:  lock file "postmaster.pid" already exists
>>>2016-08-03 08:42:39 BRT TIP: Another postmaster (PID 2968) is running
>> under the data directory "C: / Program >Files / PostgreSQL / 9.5 / data"?
>>
>> These errors point to the source of your problem. When the database is
>> shutdown imporperly
>> (as in pulling the plug or manual power down), you often get left with
>> the postmaster.pid file not beeing deleted.
>
> Or Postgres is actually running and doing the below would not be good.
>
>>
>> So just go ahead and delete /PostgreSQL/9.5/data/postmaster.pid and you
>> can then restart the PostgreSQL service.
>
> It is a good idea to verify before deleting.
>
>> *
>> --
>> *Melvin Davidson*
>> I reserve the right to fantasize.  Whether or not you
>> wish to share my fantasy is entirely up to you.
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com


--
Adrian Klaver
adrian.klaver@aklaver.com