I had some ideas about this slow flat file issue, but it's apparently
not yet much of an issue, in fact ...
Someone talked about the postmaster having to be "at arms' length"
from the actual tables. But I was looking at the postmaster code,
and it seems to fork a new backend as soon as select indicates
there's a new request, without checking authorization or anything
first. So why can't the new backend query the user table as normal?
Even if shared buffers are trashed, that'll only take down the new
backend, not the original postmaster, right?
Enlightenment welcome, or redirection to -developers if appropriate.
- John Burger
MITRE
---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
