From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Lincoln Yeoh <lylyeoh(at)mecomb(dot)com>, Serge Sozonoff <serge(at)globalbeach(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: open pgsql files (was Re: [GENERAL] Mime-Version: 1.0) |
Date: | 2000-02-22 01:32:56 |
Message-ID: | 38B1E748.6AE1182C@austin.rr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Bruce Momjian wrote:
>
> > At 03:28 PM 21-02-2000 -0600, Ed Loehr wrote:
> >
> > >Your numbers do not surprise me at all. Backend pgsql servers live
> > >for the lifetime of the client connection, and they open a similarly
> > >large number of files on my system. I throttle them by throttling the
> > >life of the apache children who are generally the only clients.
> >
> > But doesn't the backend close the files after it's done with em? Or it
> > doesn't know when it's done with the files?
> >
> Keeps files open in the expectation it may need them again.
I assumed so. "It would be nice" if one could constrain the open file
consumption of the backends directly in the same manner as sort
buffersizes, etc (i.e., setting a maximum number of files to open).
Some sort of LRU cache on file handles, maybe...worthy of a todo item?
Cheers,
Ed Loehr
From | Date | Subject | |
---|---|---|---|
Next Message | Kevin Hennessy | 2000-02-22 05:07:06 | change owner |
Previous Message | Bruce Momjian | 2000-02-22 01:20:46 | Re: open pgsql files (was Re: [GENERAL] Mime-Version: 1.0) |