On Tuesday 17 July 2007 17:47:01 Tom Lane wrote:
> [EMAIL PROTECTED] writes:
> > i think i got it fixed as i saw that i pushed my maintenance_work_mem too
> > high. It was higher than physical ram :-(
>
> Ooops, that will definitely cause problems.
yes it did! I ran it again. And now it takes 10 minutes per index instead of
10 hours (still 8.1). maybe something postgres should complain about if
setting maintance_work_mem too high.
Thanks for your help.
kind regards
janning
---------------------------(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
