Thread: AbortTransaction and not in in-progress state

AbortTransaction and not in in-progress state

From
The Hermit Hacker
Date:
Morning...

    the following is starting to get on my nerves :(  The table I'm
trying to update is ~22k records, and I can't seem to get through it...

    So, my first question is *what* does this message mean?  The
backend gives an error about too many open files, but there are less then
20 process running on this machine...

zeus:/usr/local/acctng/bin> ./close.pl isdn-1.trends.ca
processing 1405 records ... Found 1405 open records...
NOTICE:  AbortTransaction and not in in-progress state

    I suspect that this is still a 6.3.1 server, and we're planning on
moving this to another machine that has 6.3.2 installed, but I figured I'd
ask regardless...

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org


Re: [HACKERS] AbortTransaction and not in in-progress state

From
"Billy G. Allie"
Date:
>
> Morning...
>
>     the following is starting to get on my nerves :(  The table I'm
> trying to update is ~22k records, and I can't seem to get through it...
>
>     So, my first question is *what* does this message mean?  The
> backend gives an error about too many open files, but there are less then
> 20 process running on this machine...

There are two limits on the number of open files in UNIX systems (ok, three, if your C library imposes it's own limit
onthe number of FILE *), the system wide limit and the per process limit.  The per process limit is usually much
smallerthan the system wide limit (i.e 60 vs. 400).  It is therefor possible that the backend process is running out of
filehandles, even though there are plenty of file handles available on a system wide bases. 

I hope this helps.

Billy G. Allie.