pg.ddx.io  pgsql-php@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Joshua D. Drake <jd@commandprompt.com>
To: Yulius Tjahjadi <yulius@xfire.com>
Cc: pgsql-php@postgresql.org
Subject: Re: pg_pconnect causing
Date: Tue, 15 Mar 2005 21:01:58 -0800
Message-ID: <4237BDC6.9070107@commandprompt.com> (raw)
In-Reply-To: <08F5636B48FE8F4D856E209D0E6C0637A83BC3@hq01.ultimatearena.com>
References: <08F5636B48FE8F4D856E209D0E6C0637A83BC3@hq01.ultimatearena.com>

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

Attachments:

jd.vcf (text/x-vcard, 283B) download 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

view thread (3+ messages)  latest in thread

Message-ID: <4237BDC6.9070107@commandprompt.com>
Permalink:  ../4237BDC6.9070107@commandprompt.com/
Also on:    postgresql.org/message-id/4237BDC6.9070107@commandprompt.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-php@postgresql.org
  Cc: jd@commandprompt.com, yulius@xfire.com
  Subject: Re: pg_pconnect causing
  In-Reply-To: <4237BDC6.9070107@commandprompt.com>
  References: <08F5636B48FE8F4D856E209D0E6C0637A83BC3@hq01.ultimatearena.com> <4237BDC6.9070107@commandprompt.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox