Re: [PERFORM] could not send data to client: Broken pipe
Pradeep Parmar wrote: Hi, I'm using Postgres 7.4. I have a web application built with php4 using postgres7.4 I was going through /var/log/messages of my linux box ( SLES 9). I encountered the following messages quite a few times. postgres[20199]: [4-1] ERROR: could not send data to client: Broken pipe postgres[30391]: [6-1] LOG: could not send data to client: Broken pipe postgres[30570]: [6-1] LOG: could not send data to client: Broken pipe Can anyone help me in interpreting these messages? What is causing this error msg? What is the severity? Not really a performance question, but at a guess your client went away. Is there anything to indicate this in your php/apache logs? Can you reproduce it by hitting cancel in your web-browser? -- Richard Huxton Archonet Ltd ---(end of broadcast)--- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
Re: [PERFORM] could not send data to client:
Justin wrote: I have 6 Windows PC in a test environment accessing a very small Postgres DB on a 2003 Server. The PC's access the database with a cobol app via ODBC. 3 of the PC's operate very efficiently and quickly. 3 of them do not. The 3 that do not are all new Dell XP Pro with SP2. They all produce the error in the log file as below: 2005-06-16 16:17:30 LOG: could not send data to client: No connection could be made because the target machine actively refused it. 2005-06-16 16:17:30 LOG: could not receive data from client: No connection could be made because the target machine actively refused it. 2005-06-16 16:17:30 LOG: unexpected EOF on client connection [...] Have you tried other ODBC app (excel, etc) to connect to the database from the machines? If so and it works, 1. what version odbc driver 2. what cobol compiler 3. what technology to map cobol i/o to sql (Acu4GL for example) This is probably more appropriate on pgsql-odbc and plain text is preferred for these mailing lists. Merlin ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
