pg.ddx.io pgsql-php@postgresql.org mailing list archivehelp / color / mirror / Atom feed
pg_pconnect causing 3+ messages / 2 participants [nested] [flat]
* pg_pconnect causing @ 2005-03-16 02:27 Yulius Tjahjadi <yulius@xfire.com> 0 siblings, 1 reply; 3+ messages in thread From: Yulius Tjahjadi @ 2005-03-16 02:27 UTC (permalink / raw) To: pgsql-php 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: pg_pconnect causing @ 2005-03-16 05:01 Joshua D. Drake <jd@commandprompt.com> parent: Yulius Tjahjadi <yulius@xfire.com> 0 siblings, 0 replies; 3+ messages in thread From: Joshua D. Drake @ 2005-03-16 05:01 UTC (permalink / raw) To: Yulius Tjahjadi <yulius@xfire.com>; +Cc: pgsql-php 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:^ permalink raw reply [nested|flat] 3+ messages in threadjd.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
* Re: pg_pconnect causing @ 2005-03-16 19:07 Yulius Tjahjadi <yulius@xfire.com> 0 siblings, 0 replies; 3+ messages in thread From: Yulius Tjahjadi @ 2005-03-16 19:07 UTC (permalink / raw) To: Joshua D. Drake <jd@commandprompt.com>; +Cc: pgsql-php 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 ^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2005-03-16 19:07 UTC | newest] Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2005-03-16 02:27 pg_pconnect causing Yulius Tjahjadi <yulius@xfire.com> 2005-03-16 05:01 ` Joshua D. Drake <jd@commandprompt.com> 2005-03-16 19:07 Re: pg_pconnect causing Yulius Tjahjadi <yulius@xfire.com>
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