Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove - Mailing list pgsql-general

From Fujii Masao
Subject Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove
Date
Msg-id CAHGQGwF1kEpVn+FFcF+AZhvV7BmMVOKiYcanhDMr0JgMfyp7PA@mail.gmail.com
Whole thread Raw
In response to Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove  (Mistina Michal <Michal.Mistina@virte.sk>)
Responses Re: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove
List pgsql-general
On Mon, Aug 26, 2013 at 9:53 PM, Mistina Michal <Michal.Mistina@virte.sk> wrote:
> Hi there.
>
> I didn’t find out why this issue happened. Only backup and format of the
> filesystem where corrupted postmaster.pid file existed helped to get rid of
> it. Hopefully the file won’t appear in the future.

I have encountered similar problem when I broke the filesystem by
a double mount. You may have gotten the same problem.

>  Master/Slave Set: ms_drbd_pg [drbd_pg]
>
>      Masters: [ tstcaps01 ]
>
>      Slaves: [ tstcaps02 ]

Why do you use DRBD with streaming replicatin? If you locates
the database cluster on DRBD, it's better to check the status of
DRBD filesystem.

Regards,

--
Fujii Masao


pgsql-general by date:

Previous
From: Mistina Michal
Date:
Subject: Re: postmaster.pid still exists after pacemaker stopped postgresql - how to remove
Next
From: Samrat Revagade
Date:
Subject: Re: effective_io_concurrency with an SSD SAN?