Re: Problems with C Language Functions after upgrade to 7.3.2 - Mailing list pgsql-admin

From Tom Lane
Subject Re: Problems with C Language Functions after upgrade to 7.3.2
Date
Msg-id 3485.1049820142@sss.pgh.pa.us
Whole thread Raw
In response to Re: Problems with C Language Functions after upgrade to 7.3.2  (Stefan Holzheu <stefan.holzheu@bitoek.uni-bayreuth.de>)
List pgsql-admin
Stefan Holzheu <stefan.holzheu@bitoek.uni-bayreuth.de> writes:
> In 7.1.3 triggers worked fine. With 7.3.2 triggers work in most cases
> but in some cases execution fails at fork or exec.

>> Fails how?  What's the error code exactly?

> fork: errno 2  /* No such file or directory */
> exec: errno 11 /* Try again */

Hmm.  You mean the other way round, I assume, because ENOENT surely
makes no sense for fork().

System resource exhaustion problems, maybe?  EAGAIN for fork() strongly
suggests that.  Perhaps you are running into a ulimit-like limit, such
as max processes per user?  Not sure about ENOENT --- are you giving an
absolute path to locate the program to execute?

            regards, tom lane


pgsql-admin by date:

Previous
From: Stefan Holzheu
Date:
Subject: Re: Problems with C Language Functions after upgrade to 7.3.2
Next
From: Jeff Boes
Date:
Subject: pg_class.reltuples not reset by VACUUM?