Tom Lane wrote:
Stephen Marshall [EMAIL PROTECTED] writes:
2. The histogram concept is a neat idea, but I think some reorganization
of the page information might make it unnecessary. Currently the FSM
pages are sorted by BlockNumber. This was particularly useful for
adding
Tom,
I'm happy to see your attentions turning back to the FSM. I like the
design, but I do have a few suggestions, particularly about how to
handle oversubscription of the FSM.
1. When the FSM is oversubscribed and one is trying to decide which
pages to keep, remember that page info is
The following is a proposal for work I'd like to do to force
long-running backend processes to reprepare their prepared statements.
It would be used in cases where the user knows they have made a database
change that will invalidate an existing prepared statement.
I look forward to comments