Re: [Win32] Problem with rename() - Mailing list pgsql-bugs

From Peter Brant
Subject Re: [Win32] Problem with rename()
Date
Msg-id 4444EA7B020000BE00002F76@gwmta.wicourts.gov
Whole thread Raw
In response to Re: [Win32] Problem with rename()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [Win32] Problem with rename()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Does that also explain why an attempt to make a new connection just
hangs?

One other thing regarding that is that connection attempt seems to
kinda, sorta succeed.  It never makes it as far as a command prompt, but
on the "stop -m immediate", psql does print the "HINT:  In a moment you
should be able to reconnect to the database and repeat your command.",
etc. log messages.

Pete

>>> Tom Lane <tgl@sss.pgh.pa.us> 04/18/06 8:03 pm >>>
I looked into this and found out that in fact, InstallXLogFileSegment
holds the ControlFileLock while trying to rename the WAL segment file.
It does this specifically as an interlock against someone else trying
to create the same new WAL segment name.  So once the system runs out
of already-created WAL segments, XLogFileInit hangs up on the lock,
and then anything that wants to generate WAL entries is blocked.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [Win32] Problem with rename()
Next
From: Tom Lane
Date:
Subject: Re: [Win32] Problem with rename()