Hi all,
>> 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?
>>
>> I've really nothing against native americans, is there a way to throttle or
>> fix our good ol elephant instead?
>
>Keeps files open in the expectation it may need them again.
Well, is there not a way to tell Postgres to close the files when he is
finished?
If I have 40 tables and each table is made up of 6-7 files including
index's etc then that
means that per process I could be opening up to 200-240 !!
This means that with 64 db connections I could be hitting 12800-15360 open
files
on my system!!! What is the current Linux limit without kernel re-compile?
What is the Linux
limit with kernel re-compile?
Why can't I just tell postgres to close thos files say 2 minutes after he
is done with them
and they have been idle?
Thanks, Serge
