"Craig A. James" <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> Given the sizes of the tables involved, you'd likely have to boost up
>> work_mem before the planner would consider a hash join. What nondefault
>> configuration settings do you have, anyway?
> shared_buffers = 20000
> work_mem = 32768
> effective_cache_size = 300000
So for a 6M-row table, 32M work_mem would allow ... um ... 5 bytes per
row. It's not happening :-(
Try boosting work_mem by a factor of 100 and seeing whether a hash-based
join actually wins or not. If so, we can discuss where the sane setting
really falls, if not there's no point.
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
