On Saturday May 6 2006 7:15 pm, Ed L. wrote:
> I'm watching a long, painfully slow 60GB load from pg_dump
> (8.1.2), and noticing it's jumping back and forth from
> different tables. I assume this is the index creation order
> showing up.
>
> Would it make more sense to have pg_dump dump indexes grouped
> by the table? That way, if a table got loaded into cache for
> one index creation, it might still be there for the immediatly
> following index creations on the same table...
And would same idea work for ordering of constraint adding...?
Ed
---------------------------(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
