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

Re: [Win32] Problem with rename()

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>,<pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [Win32] Problem with rename()
Date: 2006-04-18 11:12:06
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
> Hi all,
> In the last couple of days, we've been bitten (a couple of 
> times, on different servers) by an apparent glitch or bad 
> interaction in the Windows implementation of rename().
> The relevant log message is:
> [2006-04-17 16:49:22.583 ] 2252 LOG:  could not rename file 
> "pg_xlog/000000010000010A000000BD" to 
> "pg_xlog/000000010000010A000000D7", continuing to try
> It apparently just keeps on looping indefinitely.  The 
> "completed rename" message from port/dirmod.c never shows up.
> Shortly thereafter, Postgres becomes unresponsive.  Attempts 
> to make a new connection just block.  Autovacuums block.  A 
> "pg_ctl ... stop -m fast" doesn't work.  Only "pg_ctl ... 
> stop -m immediate" does.
> With the last occurrence, I saved off the output of "handle 
> -a" and "pslist -x" in case that's helpful.  
> Any thoughts on what might be going wrong?  If it happens 
> again, what other clues should I be looking for?

It would be interesting to see which processes have handle(s) open to
either of these two names. "handle -a" shuold give that, I assume?


pgsql-bugs by date

Next:From: Bruce MomjianDate: 2006-04-18 12:39:52
Subject: Re: [ BUG in logs]
Previous:From: Dave PageDate: 2006-04-18 07:28:13
Subject: Re: BUG #2399: Postgis DLL corrupted

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