Home > Archive > PHP with PostgreSQL Database > March 2005 > pg_pconnect causing
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
pg_pconnect causing
|
|
| Yulius Tjahjadi 2005-03-29, 9:02 pm |
| 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
| |
| Joshua D. Drake 2005-03-29, 9:02 pm |
| 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
| |
| Yulius Tjahjadi 2005-03-29, 9:02 pm |
| Thanks. I'll go bug the php guys.
yulius
-----Original Message-----
From: Joshua D. Drake [mailto:jd@commandprompt.com]
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
>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
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
|
|
|
|
|