dbTalk Databases Forums  

Applicationl Crash - Connection reset by peer !!!

comp.databases.postgresql.novice comp.databases.postgresql.novice


Discuss Applicationl Crash - Connection reset by peer !!! in the comp.databases.postgresql.novice forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
Pradeepkumar, Pyatalo
 
Posts: n/a

Default Applicationl Crash - Connection reset by peer !!! - 09-01-2004 , 06:43 AM







Hi,

I am using Postgresql 7.4.3 running on RedHat Linux 2.4.7. My Application is
coded in C. I am using libpq functions inorder to connect to the database.
I am using PQsetdbLogin() to connect and PQfinish() to release the database
connection. In my application I have around 15-20 C functions. In each
function i connect to the database, perform some query and then release the
connection. Today the application is crashing. It says SEGMENTATION FAULT in
PQsetdbLogin().
In the LOG, I see -
LOG: could not receive data from client: broken pipe
LOG: connection reset by peer
LOG: unexpected EOF on client connection.

any inputs on this most welcome.
Thanks in advance.
Quote:
With Best Regards
Pradeep Kumar P J

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster



Reply With Quote
  #2  
Old   
Tom Lane
 
Posts: n/a

Default Re: Applicationl Crash - Connection reset by peer !!! - 09-01-2004 , 09:27 AM






"Pradeepkumar, Pyatalo (IE10)" <Pradeepkumar.Pyatalo (AT) honeywell (DOT) com> writes:
Quote:
I am using Postgresql 7.4.3 running on RedHat Linux 2.4.7. My Application is
coded in C. I am using libpq functions inorder to connect to the database.
I am using PQsetdbLogin() to connect and PQfinish() to release the database
connection. In my application I have around 15-20 C functions. In each
function i connect to the database, perform some query and then release the
connection. Today the application is crashing. It says SEGMENTATION FAULT in
PQsetdbLogin().
The odds are *extremely* high that this is a bug in your own code, not
in libpq. PQsetdbLogin() is probably just the victim of a memory stomp
occurring elsewhere.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo (AT) postgresql (DOT) org



Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.