ISSUE after upgrading to POSTGRES 8.4.8

On 30.04.2013 09:40, Bansal, Pradeep wrote:

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

ISSUE:-
===========================================================================
SEQUENCE STATEMENTS = 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.
=============================================================================

The above error is seen after postgress restart/fresh installation couple of times. While executing the same query thrice and so on it runs as expected.

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

You didn't mention what version you upgraded from, but in any case, you
should at least upgrade to the latest 8.4.x minor release, which is
8.4.17. There have been a lot of bugs fixed between 8.4.8 and 8.4.17. I
don't know if any of them explain the issue you're seeing, but there's
not much point debugging it further before you upgrade.

- Heikki

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

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
the 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

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:-
=================
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 with (
<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: DEFAULT; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<%2013-04-30 15:05:55 IST>DEBUG: forked new backend, pid=4703 socket=7
<sfmdb%2013-04-30 15:05:55 IST>DEBUG: CommitTransaction
<sfmdb%2013-04-30 15:05:55 IST>DEBUG: name: unnamed; blockState: STARTED; state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
<sfmdb%2013-04-30 15:05:55 IST>DEBUG: parse <unnamed>: SELECT nextval('"serial1"')
<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: DEFAULT; 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>: SELECT 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: STARTED; 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: DEFAULT; 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)

====================

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 the 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

On 4/30/2013 2:55 AM, Bansal, Pradeep wrote:

Also with the debug5 mode the logs are:-

well, I don't see any backend crashes there.

--
john r pierce 37N 122W
somewhere on the middle of the left coast