I take that back.  My local Postgres just didn't have stats_block_level
and stats_row_level turned on.  It happens on single processor machines


>>> "Peter Brant" <[EMAIL PROTECTED]> 05/02/06 6:29 pm >>>
minutes.  Single processor machines don't seem to be affected.

---------------------------(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

Reply via email to