[Win32] Problem with rename()

From: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
To: <pgsql-bugs(at)postgresql(dot)org>
Subject: [Win32] Problem with rename()
Date: 2006-04-17 23:53:56
Message-ID: 4443E444020000BE00002ED6@gwmta.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

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?

Pete

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Bruce Momjian 2006-04-18 00:52:30 Re: [martin@bugs.unl.edu.ar: BUG in logs]
Previous Message Peter Brant 2006-04-17 23:35:39 Re: Permission denied on fsync / Win32 (was right

Browse pgsql-patches by date

  From Date Subject
Next Message Peter Eisentraut 2006-04-18 00:12:00 Re: pg_ctl options checking
Previous Message Simon Riggs 2006-04-17 22:13:07 Re: pg_ctl options checking