"Jonah H. Harris" <[EMAIL PROTECTED]> writes:
> On Feb 5, 2008 11:54 PM, Decibel! <[EMAIL PROTECTED]> wrote:
>> One of the things that drew me to Postgres years ago was that I could
>> actually read about how it works in a clear, concise manner.
> Agreed.
Not sure how you could argue "concise" as a benefit here.
There are literally thousands of aspects of the PG codebase that could
impact performance in user-visible ways. Most of them are not
documented in the SGML docs. If we tried to expose all that, the docs
would become completely unreadable. (I just got done reading some
slashdot griping about how our docs are already too long and too
complicated for novices, so I'm not feeling particularly charitable
about proposals to dump even more seldom-useful details into them.)
I'm really not seeing the case for user-level documentation of HOT,
when for instance most of the planner's optimization behavior is not
so documented.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
