From: | Marc Tardif <admin(at)wtbwts(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | handling multiple file descriptors |
Date: | 2000-02-19 01:26:11 |
Message-ID: | Pine.BSF.4.10.10002190119010.18788-100000@server.b0x.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I've been trying to figure out how postgresql handles multiple open file
descriptors. First, I have managed to find out postgresql keeps a pool of
available descriptors for general processing tasks like sorting for
example. Second, I have tried to find what kind of data structure was used
for open descriptors to tables and indices, but couldn't find where. Could
someone please let me know what kind of data structure(s) is/are used for
open file descriptors and where this is located in the code?
The reason I'm so curious about such a specific part of the code is that
this problem has often occured in my own source code. In the past, I have
used a linked list and contemplated using a hash table to manage multiple
open file descriptors. I'm therefore interested to find out what real
production systems use for this kind of problem.
Regards,
Marc Tardif
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2000-02-19 01:36:41 | Re: [HACKERS] Re: SQL compliance - why -- comments only at psql level ? |
Previous Message | Roberto Cornacchia | 2000-02-19 01:23:38 | Generalized Top Queries on PostgreSQL |