Skip site navigation (1) Skip section navigation (2)

Re: [Win32] Problem with rename()

From: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [Win32] Problem with rename()
Date: 2006-04-18 18:32:43
Message-ID: 4444EA7B020000BE00002F76@gwmta.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-bugspgsql-patches
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(at)sss(dot)pgh(dot)pa(dot)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.


In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2006-04-18 18:44:32
Subject: Re: [Win32] Problem with rename()
Previous:From: Tom LaneDate: 2006-04-18 18:03:40
Subject: Re: [Win32] Problem with rename()

pgsql-patches by date

Next:From: Tom LaneDate: 2006-04-18 18:44:32
Subject: Re: [Win32] Problem with rename()
Previous:From: Tom LaneDate: 2006-04-18 18:03:40
Subject: Re: [Win32] Problem with rename()

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group