Re: ISSUE after upgrading to POSTGRES 8.4.8

Hi John,

Thanks for the reply.
If I execute the query directly in the db(not through my program) then this=
 scenario is not at all reproducible.
Also with the debug5 mode the logs are:-
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Removing lock file (/var/opt/psb/data/STANDALONE_LOCK)
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  received password packet
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  postmaster child[4703]: starting wit=
h (
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:   postgres
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:   -v196608
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:   -y
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:   RAIDSAPROVDB
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  )
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  InitPostgres
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  my backend id is 1
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  StartTransaction
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  name: unnamed; blockState:       DEF=
AULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<%2013-04-30 15:05:55 IST>DEBUG:  forked new backend, pid=3D4703 socket=3D7
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  CommitTransaction
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  name: unnamed; blockState:       STA=
RTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  parse <unnamed>: SELECT nextval('"se=
rial1"')
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  StartTransactionCommand
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  StartTransaction
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  name: unnamed; blockState:       DEF=
AULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<sfmdb%2013-04-30 15:05:55 IST>LOG:  duration: 25.215 ms  parse <unnamed>: =
SELECT nextval('"serial1"')
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  bind <unnamed> to <unnamed>
<sfmdb%2013-04-30 15:05:55 IST>LOG:  duration: 0.089 ms  bind <unnamed>: SE=
LECT nextval('"serial1"')
<sfmdb%2013-04-30 15:05:55 IST>LOG:  duration: 4.061 ms  execute <unnamed>:=
 SELECT nextval('"serial1"')
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  CommitTransactionCommand
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  CommitTransaction
<sfmdb%2013-04-30 15:05:55 IST>DEBUG:  name: unnamed; blockState:       STA=
RTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<sfmdb%2013-04-30 15:05:56 IST>DEBUG:  parse <unnamed>: INSERT INTO RAWLOG =
(boottime, hidden, id, rawdata, source, version) VALUES ($1, $2, $3, $4, $5=
, $6)
<sfmdb%2013-04-30 15:05:56 IST>DEBUG:  StartTransactionCommand
<sfmdb%2013-04-30 15:05:56 IST>DEBUG:  StartTransaction
<sfmdb%2013-04-30 15:05:56 IST>DEBUG:  name: unnamed; blockState:       DEF=
AULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<sfmdb%2013-04-30 15:05:56 IST>LOG:  duration: 30.224 ms  parse <unnamed>: =
INSERT INTO RAWLOG (boottime, hidden, id, rawdata, source, version) VALUES =
($1, $2
, $3, $4, $5, $6)

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

Please let me know your thoughts.

Regards
Pradeep B

From: John R Pierce [mailto:pierce@hogranch.com]
Sent: Tuesday, April 30, 2013 1:24 PM
To: Bansal, Pradeep; pgsql-bugs@postgresql.org
Subject: Re: [BUGS] ISSUE after upgrading to POSTGRES 8.4.8

On 4/29/2013 11:40 PM, Bansal, Pradeep wrote:
PQdb name : RAIDSAPROVDB : server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

you need to look at the server log after an error like this, and see WHY th=
e server terminated

but I concurr with Heikki, upgrade to 8.4.latest (currently 8.4.17) and if =
this still occurs then figure out why.



--

john r pierce                                      37N 122W

somewhere on the middle of the left coast