Broken pipes - Mailing list pgsql-general

From mike sears
Subject Broken pipes
Date
Msg-id 000d01c15e61$e3e244e0$fa00000a@wyd2002.org
Whole thread Raw
Responses Re: Broken pipes  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: Broken pipes 2  (schemy@freesurf.fr)
List pgsql-general
Recently I've been noticing a lot of odd errors in our postgres logs, that involves a great deal of broken pipes and pq_recvbuf entries. I only noticed this when tables were not being created and am not sure what exactly is going on.
 
this is just a small bit of what keeps popping up in my logs, and if someone could help explain whats going on would be greatly apreciated.
 
NOTICE:  CREATE TABLE will create implicit sequence 'faq_id_seq' for SERIAL column 'faq.id'
NOTICE:  CREATE TABLE/PRIMARY KEY will create implicit index 'faq_pkey' for table 'faq'
DEBUG:  ProcessUtility: create table faq(id serial, ref int8, body text, status char(1) DEFAULT 'N' NOT NULL, primary key(id));
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
pq_recvbuf: unexpected EOF on client connection
DEBUG:  ProcessUtility: create table faq(id serial, ref int8, body text, status char(1) DEFAULT 'N' NOT NULL, primary key(id));
DEBUG:  ProcessUtility: create table faq(id serial, ref int8, body text, status char(1) DEFAULT 'N' NOT NULL, primary key(id));
pq_flush: send() failed: Broken pipe
pq_recvbuf: recv() failed: Broken pipe
 
 
Mike

pgsql-general by date:

Previous
From: "Eric Ridge"
Date:
Subject: Re: Sorting by parent/child relationships
Next
From: Alvaro Herrera
Date:
Subject: Re: UNIQUE constraint violations and transactions