Re: Problems with DBI, DBD::Pg and Postgres 7.2.
От | Tom Lane |
---|---|
Тема | Re: Problems with DBI, DBD::Pg and Postgres 7.2. |
Дата | |
Msg-id | 25787.1014491951@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Problems with DBI, DBD::Pg and Postgres 7.2. (Johan Mjönes <johan.mjones@agent25.se>) |
Список | pgsql-general |
=?iso-8859-1?Q?Johan_Mj=F6nes?= <johan.mjones@agent25.se> writes: > We can reproduce this as many times as we want - it always crashes on > the same position, but no matter what the query! Odd. The postmaster log fragment you show contains no indication that there's anything wrong, AFAICS. Even odder, there's no complaint about an unexpected client disconnect, so it would seem that the client side sent a deliberate disconnect (X) command. One idea that comes to mind is that perhaps either the client or server side is running under "ulimit" restrictions that kick in right here. That doesn't seem to explain your symptoms, but some related idea might be the right answer. It might be possible to learn something by attaching to the backend process with gdb and setting a breakpoint at proc_exit, so you could see where it's being called from. If it's not reacting to an "X" command then we'd learn what is making it exit. regards, tom lane
В списке pgsql-general по дате отправления: