ISSUE after upgrading to POSTGRES 8.4.8 - Mailing list pgsql-bugs

Hello,


I have observed the below issue after upgrading to the above mentioned vers=
ion of postgress. Any help is very much appreciated:-

ISSUE:-
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
SEQUENCE STATEMENTS =3D SELECT nextval('"serial1"')
PQstatus(m_connection) :- CONNECTION OK
PQdb name : RAIDSAPROVDB : server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D

The above error is seen after postgress restart/fresh installation couple o=
f times. While executing the same query thrice and so on it runs as expecte=
d.

I am not able to understand that why it is getting failed initially. ???? k=
indly let me know if this is an existing bug in the postgress or any fix av=
ailable for the same.

Looking forward to your reply.

Regards
Pradeep Bansal