Re: [Win32] Problem with rename()

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [Win32] Problem with rename()
Date: 2006-04-18 17:09:09
Message-ID: 14774.1145380149@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-patches

"Peter Brant" <Peter(dot)Brant(at)wicourts(dot)gov> writes:
> [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.

BTW, whatever we decide to do about the rename problem, I'd say that the
second point represents an independent bug. The rename loop would hang
up the bgwriter, which would probably cause performance to tank, but the
rest of the system shouldn't become completely unresponsive because of
an incomplete checkpoint. The checkpoint operation shouldn't be holding
any critical locks at this point.

Can you find out anything about what the other processes are blocking on?

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Magnus Hagander 2006-04-18 17:24:32 Re: Permission denied on fsync / Win32 (was right
Previous Message Tom Lane 2006-04-18 17:04:16 Re: Permission denied on fsync / Win32 (was right

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-04-18 18:03:40 Re: [Win32] Problem with rename()
Previous Message Peter Brant 2006-04-18 15:50:39 Re: [Win32] Problem with rename()