"Peter Brant" <[EMAIL PROTECTED]> 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
