Re: pqReadData() -- backend closed the channel unexpectedly.
От | Jeff Barrett |
---|---|
Тема | Re: pqReadData() -- backend closed the channel unexpectedly. |
Дата | |
Msg-id | 9f0rhn$1594$1@news.tht.net обсуждение исходный текст |
Ответ на | Re: pqReadData() -- backend closed the channel unexpectedly. (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Re: pqReadData() -- backend closed the channel unexpectedly.
|
Список | pgsql-admin |
Checked that out, every row has a value and the values are properly formatted. Seems like this may be an issue of not enough ram in the server. The only problem I have with that diagnosis is that I do not get an out of memory error, I just loose the back end. Thanks, Jeff "Tom Lane" <tgl@sss.pgh.pa.us> wrote in message news:12678.991063302@sss.pgh.pa.us... > "Jeff Barrett" <jbarrett@familynetwork.com> writes: > > I get a success on testtime and a failure of "pqReadData() -- backend > > closed the channel unexpectedly on logs2". > > > update <either tablename> set time2 = to_timestamp(time, 'HH24:MI:SS'); > > Any NULL values in the time column? ISTR to_timestamp fails on NULLs in > pre-7.1 releases. Try upgrading. > > regards, tom lane > > ---------------------------(end of broadcast)--------------------------- > TIP 2: you can get off all lists at once with the unregister command > (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
В списке pgsql-admin по дате отправления: