Re: FATAL: lock file "postmaster.pid" already exists

From: deepak <deepak(dot)pn(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alban Hertroys <haramrae(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org, markdilger(at)yahoo(dot)com
Subject: Re: FATAL: lock file "postmaster.pid" already exists
Date: 2012-05-23 16:03:33
Message-ID: CAALYutfpCfMr=7GMEMNCmXbHDf6fLLvs5vXrocsZFr1wr_jw5A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks, I have put one of the other developers working on this issue, to
comment.

--
Deepak

On Mon, May 21, 2012 at 10:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> deepak <deepak(dot)pn(at)gmail(dot)com> writes:
> > We could reproduce the start-up problem on Windows 2003. After a reboot,
> > postmaster, in its start-up sequence cleans up old temporary files, and
> > this step used to take several minutes (a little over 4 minutes),
> delaying
> > the writing of line 6 onwards into the PID file. This delay caused pg_ctl
> > to timeout, leaving behind an orphaned postgres.exe process (which
> > eventually forks off many other postgres.exe processes).
>
> Hmm. It's easy enough to postpone temp file cleanup till after the
> postmaster's PID file is completely written, so I've committed a patch
> for that. However, I find it mildly astonishing that such cleanup could
> take multiple minutes. What are you using for storage, a man with an
> abacus?
>
> regards, tom lane
>

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Alberto Zanon 2012-05-23 16:08:56 Re: Migrating from 8.2 to 9.1 : invalid port number
Previous Message Bartosz Dmytrak 2012-05-23 15:54:00 Re: Up-to-date reports database