Re: Warning: Don't delete those /tmp/.PGSQL.* files

On Sat, Nov 25, 2000 at 05:35:13PM -0500, some SMTP stream spewed forth:
*snip*
>
> > So, I began restarting pgsql w/a line like
>
> > rm -f /tmp/.PGSQL.* && postmaster -i >log 2>log &
>
> > Which works great. Except that I *kept* using this for two weeks
> > after the view problem (damn that bash up-arrow laziness!), and
> > yesterday, used it to restart PostgreSQL except (oops!) it was
> > already running.
>
> > Results: no database at all. All classes (tables/views/etc) returned
> > 0 records (meaning that no tables showed up in psql's \d, since
> > pg_class returned nothing.)
>

*snip Tom's reply*
I have a situation vaguely related to this.
At some point Postgres was not shut down properly and now everytime at
startup I the error log gets something like:

---------
root% tail -f errlog
Waiting for postmaster starting up...DEBUG: Data Base System is starting
up at Sat Nov 25 16:53:10 2000
DEBUG: Data Base System was interrupted being in production at Sat Nov
25 16:35:27 2000
DEBUG: Data Base System is in production state at Sat Nov 25 16:53:10
2000
FATAL 1: ReleaseLruFile: No open files available to be closed
............................................................pg_ctl:
postmaster does not start up
---------

After that, all postgres processes die and the cycle begins again on
subsequent attempts to start postgres.
At one point I would receive some "Too many open files" (or similar)
error with postgres holding more than 750 file descriptors -- almost
entirely consisting of socket streams.
What is the significance of "ReleaseLruFile" and how can I repair this?

This is using FreeBSD 4.1-RELEASE and Postgres 7.0.2.

Thanks

gh