Thread: [BUGS] BUG #14805: Issue with Duplicate entry

[BUGS] BUG #14805: Issue with Duplicate entry

From
rani.renu@gmail.com
Date:
The following bug has been logged on the website:

Bug reference:      14805
Logged by:          renu rani
Email address:      rani.renu@gmail.com
PostgreSQL version: 9.3.1
Operating system:   Linux ( red hat 6)
Description:

We have one perl script that is opening DB connection and performing insert
into database . When duplicate entry coming in the query , Postgre
forcefully killing process itself and in postgre log " unexpected EOF on
client connection" error is coming.
This issue in not coming every time.

Below is the log data for reference. 

<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> ERROR:  duplicate key violates
unique constraint "abc_pkey"
<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> STATEMENT:  insert into ab (id,
patch) values ('AB0202', 'V3.2.1-N904')
<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> LOG:  unexpected EOF on client
connection
<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> DEBUG:  proc_exit(0)
<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> DEBUG:  shmem_exit(0)
<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> LOG:  disconnection: session
time: 0:00:01.44 user=renu database=hydrastordb host=xxx.0.0.1 port=xxxx
<127.0.0.1(32851)%2009-01-20 04:05:07 GMT> DEBUG:  exit(0)


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

Re: [BUGS] BUG #14805: Issue with Duplicate entry

From
Alvaro Herrera
Date:
rani.renu@gmail.com wrote:
> The following bug has been logged on the website:
> 
> Bug reference:      14805
> Logged by:          renu rani
> Email address:      rani.renu@gmail.com
> PostgreSQL version: 9.3.1
> Operating system:   Linux ( red hat 6)
> Description:        
> 
> We have one perl script that is opening DB connection and performing insert
> into database . When duplicate entry coming in the query , Postgre
> forcefully killing process itself and in postgre log " unexpected EOF on
> client connection" error is coming.

You seem to be misdiagnosing this problem.  The client is closing the
connection upon getting the error, and then the server logs the fact
that the client closed the connection.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


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