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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: deepak <deepak(dot)pn(at)gmail(dot)com>
Cc: Alban Hertroys <haramrae(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: FATAL: lock file "postmaster.pid" already exists
Date: 2012-05-22 02:55:22
Message-ID: 16472.1337655322@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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 Craig Ringer 2012-05-22 04:31:50 Re: Concerning about Unicode-aware string handling
Previous Message Raymond O'Donnell 2012-05-21 21:55:58 Re: varchar for loops possible?