""Craig A. James"" <[EMAIL PROTECTED]> wrote
> I'm having a rare but deadly problem. On our web servers, a process
> occasionally gets stuck, and can't be unstuck. Once it's stuck, all
> Postgres activities cease. "kill -9" is required to kill it --
> signals 2 and 15 don't work, and "/etc/init.d/postgresql stop" fails.
>
> Details:
>
> Postgres 8.0.3
>
[Scanning 8.0.4 ~ 8.0.7 ...] Didn't find related bug fix in the upgrade
release. Can you attach to the problematic process and "bt" it (so we
could see where it stucks)?
Regards,
Qingqing
---------------------------(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
