---------------------------- Original Message ----------------------------
Subject: Abrupt close of pgsql backend
From: "Deepa K" <[EMAIL PROTECTED]>
Date: Mon, October 25, 2004 8:04 pm
To: [EMAIL PROTECTED]
--------------------------------------------------------------------------
Hi,
I am running postgresql 7.1.3 in RedHat Linux 7.2. From an external C
application, three connections are established with postmaster (it is
started with -i option) through unix sockets. Two times I received EPIPE
error when trying to send a query to postmaster. This is because of the
abrupt closure of pgsql backend.
The query sent is formed dynamically and hence I'm unable to get
the query whose processing may have led to such abrupt closure. But this
application is working for 2 years till now without any such
problems. So I don't really suspect the query.
The postgresql todo lists that usage of views can lead to
such abrupt closure. But there are no views used in my application.
The last reason, for abnormal closure that I understand is if
the hard disk is full. But this is also not the case under study.
Coming to the question,
a. What are the (other) reasons for postmaster closing
sockets abnormally?
b. How can the application detect such a abnormal closure of
socket?
--
regards,
Deepa K
--
regards,
Deepa K
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
