X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 4B18C5E46C1; Wed, 1 Sep 2004 11:27:11 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 87407-08; Wed, 1 Sep 2004 14:27:03 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 0B1BD5E4713; Wed, 1 Sep 2004 11:27:01 -0300 (ADT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i81ER6C3006304; Wed, 1 Sep 2004 10:27:06 -0400 (EDT) To: "Pradeepkumar, Pyatalo (IE10)" Cc: pgsql-novice@postgresql.org, pgsql-admin@postgresql.org Subject: Re: [NOVICE] Applicationl Crash - Connection reset by peer !!! In-reply-to: <77ED2BF75D59D1439F90412CC5B109741104F137@ie10-sahara.hiso.honeywell.com> References: <77ED2BF75D59D1439F90412CC5B109741104F137@ie10-sahara.hiso.honeywell.com> Comments: In-reply-to "Pradeepkumar, Pyatalo (IE10)" message dated "Wed, 01 Sep 2004 04:43:08 -0700" Date: Wed, 01 Sep 2004 10:27:05 -0400 Message-ID: <6303.1094048825@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=1.3 tagged_above=0.0 required=5.0 tests=PLING_PLING X-Spam-Level: * X-Archive-Number: 200409/7 X-Sequence-Number: 14710 "Pradeepkumar, Pyatalo (IE10)" writes: > 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