pg.ddx.io pgsql-sql@postgresql.org mailing list archivehelp / color / mirror / Atom feed
LOG: unexpected EOF on client connection 4+ messages / 3 participants [nested] [flat]
* LOG: unexpected EOF on client connection @ 2007-04-05 14:50 ezequias@fastcon.com.br 0 siblings, 1 reply; 4+ messages in thread From: ezequias@fastcon.com.br @ 2007-04-05 14:50 UTC (permalink / raw) To: pgsql-sql Hi list, I am doing a benchmark in my database but it is spent too much time. I was looking for my log file but I could not understad clearly what it says. The log is like this: INT: Consider increasing the configuration parameter "checkpoint_segments". LOG: checkpoints are occurring too frequently (4 seconds apart) HINT: Consider increasing the configuration parameter "checkpoint_segments". LOG: checkpoints are occurring too frequently (5 seconds apart) HINT: Consider increasing the configuration parameter "checkpoint_segments". LOG: checkpoints are occurring too frequently (5 seconds apart) HINT: Consider increasing the configuration parameter "checkpoint_segments". LOG: checkpoints are occurring too frequently (8 seconds apart) HINT: Consider increasing the configuration parameter "checkpoint_segments". NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "branches_pkey" for table "branches" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "tellers_pkey" for table "tellers" NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index "accounts_pkey" for table "accounts" ERROR: conversion between latin9 and LATIN1 is not supported STATEMENT: set client_encoding to 'latin9' FATAL: sorry, too many clients already LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection LOG: unexpected EOF on client connection Does anyone have any suggestion ? -- Ezequias Rodrigues da Rocha http://ezequiasrocha.blogspot.com ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: LOG: unexpected EOF on client connection @ 2007-04-05 15:20 Tom Lane <tgl@sss.pgh.pa.us> parent: ezequias@fastcon.com.br 0 siblings, 0 replies; 4+ messages in thread From: Tom Lane @ 2007-04-05 15:20 UTC (permalink / raw) To: ezequias@fastcon.com.br; +Cc: pgsql-sql <ezequias@fastcon.com.br> writes: > FATAL: sorry, too many clients already You need a larger max_connections setting. > LOG: unexpected EOF on client connection I think pgbench just dies ungracefully if it gets a connection failure. regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: LOG: unexpected EOF on client connection @ 2009-08-05 18:40 Bernd Nawothnig <Bernd.Nawothnig@t-online.de> 0 siblings, 1 reply; 4+ messages in thread From: Bernd Nawothnig @ 2009-08-05 18:40 UTC (permalink / raw) To: pgsql-sql Hello, A client application written in C# + npgsql 2.0.6 causes reproducable log entries like this: LOG: unexpected EOF on client connection LOG: could not receive data from client: Die Verbindung wurde vom Kommunikationspartner zurückgesetzt(*) (*) Connection reset by peer The responsable Programmer claims autovacuum caused the malfunction. But after disabling autovacuum the same error occured. Another program, written Python + psycopg2, which invokes exactly the same function resulting the above connection reset in the C# program runs without any problem while inserting far more than 10 times the amount of data the C# program should do. Even running 2 parallel instances of the Python program does not result in any error. Server is version 8.4 + Postgis 1.4 (both compiled with gcc 4.3), OS is Debian Lenny running on a Quadcore-Xeon Dell Precision 690 with 2 GB RAM. When the above error occurs the C# program is the only client connecting to the server. What may be the most probable cause of that? Bernd -- No time toulouse ^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: LOG: unexpected EOF on client connection @ 2009-08-06 02:19 Tom Lane <tgl@sss.pgh.pa.us> parent: Bernd Nawothnig <Bernd.Nawothnig@t-online.de> 0 siblings, 0 replies; 4+ messages in thread From: Tom Lane @ 2009-08-06 02:19 UTC (permalink / raw) To: Bernd.Nawothnig@web.de; +Cc: pgsql-sql Bernd Nawothnig <Bernd.Nawothnig@t-online.de> writes: > A client application written in C# + npgsql 2.0.6 causes reproducable > log entries like this: > LOG: unexpected EOF on client connection > LOG: could not receive data from client: Die Verbindung wurde vom > Kommunikationspartner zurückgesetzt(*) This just indicates that the client application closed the connection without sending a Terminate message. It's harmless, but if the log chatter annoys you, you should fix the application to close its PG connection cleanly before it quits. > The responsable Programmer claims autovacuum caused the malfunction. Nonsense ... regards, tom lane ^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2009-08-06 02:19 UTC | newest] Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed) -- links below jump to the message on this page -- 2007-04-05 14:50 LOG: unexpected EOF on client connection ezequias@fastcon.com.br 2007-04-05 15:20 ` Re: LOG: unexpected EOF on client connection Tom Lane <tgl@sss.pgh.pa.us> 2009-08-05 18:40 Re: LOG: unexpected EOF on client connection Bernd Nawothnig <Bernd.Nawothnig@t-online.de> 2009-08-06 02:19 ` Re: LOG: unexpected EOF on client connection Tom Lane <tgl@sss.pgh.pa.us>
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