Backend message type 0x44 arrived while idle
От | Oleg Bartunov |
---|---|
Тема | Backend message type 0x44 arrived while idle |
Дата | |
Msg-id | Pine.GSO.3.96.SK.990513161245.3049D-100000@ra обсуждение исходный текст |
Ответы |
Re: [HACKERS] Backend message type 0x44 arrived while idle
|
Список | pgsql-hackers |
WHile testing 6.5 cvs to see what's the progress with capability of Postgres to work with big joins I get following error messages: select a.a,at1.a as t1,at2.a as t2,at3.a as t3,at4.a as t4,at5.a as t5,a t6.a as t6,at7.a as t7,at8.a as t8,at9.a as t9,at10.a as t10 from t0 a ,t1 at1,t2 at2,t3 at3,t4 at4,t5 at5,t6 at6,t7 at7,t8 at8,t9 at9, t10 at10 where at1.a_id = a.a_id and at2.a_id=a.a_id and at3.a_id=a.a_id and at4.a_id=a.a_id and at5.a_id=a.a_id and at6.a_id=a.a_id and at7.a_id=a.a_id and at8.a_id=a.a_id and at9.a_id=a.a_id and at10.a_id=a.a_id ; Backend message type 0x44 arrived while idle Backend message type 0x44 arrived while idle We have lost the connection to the backend, so further processing is impossible. Terminating. Postgres+psql eaten all the memory+swap. Are these messages ok in such a situation ? Oleg PS. Postgres still can't serve large joins :-( _____________________________________________________________ Oleg Bartunov, sci.researcher, hostmaster of AstroNet, Sternberg Astronomical Institute, Moscow University (Russia) Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/ phone: +007(095)939-16-83, +007(095)939-23-83
В списке pgsql-hackers по дате отправления: