> Hi all,
>=20
> In the last couple of days, we've been bitten (a couple of=20
> times, on different servers) by an apparent glitch or bad=20
> interaction in the Windows implementation of rename().
>=20
> The relevant log message is:
>=20
> [2006-04-17 16:49:22.583 ] 2252 LOG: could not rename file=20
> "pg_xlog/000000010000010A000000BD" to=20
> "pg_xlog/000000010000010A000000D7", continuing to try
>=20
> It apparently just keeps on looping indefinitely. The=20
> "completed rename" message from port/dirmod.c never shows up.
>=20
> Shortly thereafter, Postgres becomes unresponsive. Attempts=20
> to make a new connection just block. Autovacuums block. A=20
> "pg_ctl ... stop -m fast" doesn't work. Only "pg_ctl ...=20
> stop -m immediate" does.
>=20
> With the last occurrence, I saved off the output of "handle=20
> -a" and "pslist -x" in case that's helpful.=20=20
>=20
> Any thoughts on what might be going wrong? If it happens=20
> 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?
//Magnus