Skip site navigation (1) Skip section navigation (2)

Re: dup(0) failed after 3195 successes: Bad file descriptor

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: operationsengineer1(at)yahoo(dot)com
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: dup(0) failed after 3195 successes: Bad file descriptor
Date: 2004-08-20 03:27:35
Message-ID: 15614.1092972455@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
<operationsengineer1(at)yahoo(dot)com> writes:
> I did a search for this error 
> *dup(0) failed after 3195 successes: Bad file descriptor*
> and came up empty as far as resolutions.

This is not an error ... it's an expected result.  If you are going to
set the log level at DEBUGn, you should expect to see a lot of
interesting-only-to-wizards chatter.

> Some references on postgresql.org archives seem to indicate it isn't
> an issue, however, when I try and check to see if postmaster is
> running via
> cygrunsrv -Q postmaster
> I get...
> Current State:  Stopped

That may be a problem, but this isn't the cause.

			regards, tom lane

In response to

Responses

pgsql-novice by date

Next:From: operationsengineer1Date: 2004-08-20 06:37:08
Subject: Re: dup(0) failed after 3195 successes: Bad file descriptor
Previous:From: operationsengineer1Date: 2004-08-20 02:19:26
Subject: dup(0) failed after 3195 successes: Bad file descriptor

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group