>Is it at all possible that the optimizer is responsible for this behaviour?
>The reason I ask is that the fact that when the inserts start the optimizer
is
>working with a very small table, as the table grows larger the optimizer
never
>learns it because no VACUUM or VACUUM ANALYZE have been run.
>
>If this is indeed the problem, then running VACUUM after every 10,000
inserts
>would solve the problem.
Can I run a vacuum while inserts are still going?