pg_pconnect causing

Hi,

When I use pg_pconnect() and the apache process exits for reaping,
I get these errors. I'm using Postgres 8.0.1 on Ferdora Core 2.

LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection
LOG: unexpected EOF on client connection

I think I know what's going on. Since there is a persistent
connection, when the apache process dies postgres thinks
the connection was abruptly disconnected w/o a proper
close function. It's not causing me any problems, but I
would like to remove any bad messages from the log file.
I was wondering if this is just a bug that needs to be
fixed.

Thanks.

yulius

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Re: pg_pconnect causing

This is a multi-part message in MIME format.
--------------090109030905050100090800
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Yulius Tjahjadi wrote:

>Hi,
>
>When I use pg_pconnect() and the apache process exits for reaping,
>I get these errors. I'm using Postgres 8.0.1 on Ferdora Core 2.
>
>LOG: unexpected EOF on client connection
>LOG: unexpected EOF on client connection
>LOG: unexpected EOF on client connection
>
>I think I know what's going on. Since there is a persistent
>connection, when the apache process dies postgres thinks
>the connection was abruptly disconnected w/o a proper
>close function. It's not causing me any problems, but I
>would like to remove any bad messages from the log file.
>I was wondering if this is just a bug that needs to be
>fixed.
>
>
You are correct in your assumption but it is not a bug.
PostgreSQL is doing exactly what it should.

The bug (if it was considered to be a bug) would be in the communication
between PHP and Apache and PHP not closing the connection before Apache
drops its process.

Sincerely,

Joshua D. Drake





>Thanks.
>
>yulius
>
>---------------------------(end of broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


--------------090109030905050100090800
Content-Type: text/x-vcard; charset=utf-8;
name="jd.vcf"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename="jd.vcf"

begin:vcard
fn:Joshua Drake
n:Drake;Joshua
org:Command Prompt, Inc.
adr:;;PO Box 215 ;Cascade Locks;OR;97014;US
email;internet:jd@commandprompt.com
title:Consultant
tel;work:503-667-4564
tel;fax:503-210-0334
x-mozilla-html:FALSE
url:http://www.commandprompt.com
version:2.1
end:vcard


--------------090109030905050100090800
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

--------------090109030905050100090800--

Re: pg_pconnect causing

Thanks. I'll go bug the php guys.

yulius

-----Original Message-----
From: Joshua D. Drake [mailto:jd@commandprompt.com]=20
Sent: Tuesday, March 15, 2005 9:02 PM
To: Yulius Tjahjadi
Cc: pgsql-php@postgresql.org
Subject: Re: [PHP] pg_pconnect causing


Yulius Tjahjadi wrote:

>Hi,
>
>When I use pg_pconnect() and the apache process exits for reaping, I=20
>get these errors. I'm using Postgres 8.0.1 on Ferdora Core 2.
>
>LOG: unexpected EOF on client connection
>LOG: unexpected EOF on client connection
>LOG: unexpected EOF on client connection
>
>I think I know what's going on. Since there is a persistent=20
>connection, when the apache process dies postgres thinks the connection

>was abruptly disconnected w/o a proper close function. It's not=20
>causing me any problems, but I would like to remove any bad messages=20
>from the log file. I was wondering if this is just a bug that needs to=20
>be fixed.
>
>
You are correct in your assumption but it is not a bug. PostgreSQL is
doing exactly what it should.

The bug (if it was considered to be a bug) would be in the communication

between PHP and Apache and PHP not closing the connection before Apache
drops its process.

Sincerely,

Joshua D. Drake





>Thanks.
>
>yulius
>
>---------------------------(end of=20
>broadcast)---------------------------
>TIP 8: explain analyze is your friend
>
>


--=20
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


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