Re: FATAL: lock file "postmaster.pid" already exists
От | deepak |
---|---|
Тема | Re: FATAL: lock file "postmaster.pid" already exists |
Дата | |
Msg-id | CAALYutfpCfMr=7GMEMNCmXbHDf6fLLvs5vXrocsZFr1wr_jw5A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: FATAL: lock file "postmaster.pid" already exists (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: FATAL: lock file "postmaster.pid" already exists
|
Список | pgsql-general |
Thanks, I have put one of the other developers working on this issue, to comment.
--
Deepak
--
Deepak
On Mon, May 21, 2012 at 10:55 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
deepak <deepak.pn@gmail.com> writes:Hmm. It's easy enough to postpone temp file cleanup till after the
> 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).
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
В списке pgsql-general по дате отправления: