On 7 May 2013 01:23, <mark.kirkwood@catalyst.net.nz> wrote:
> I'm thinking that a variant of (2) might be simpler to inplement:
>
> (I think Matt C essentially beat me to this suggestion - he originally
> discovered this issue). It is probably good enough for only *new* plans to
> react to the increased/increasing number of in progress rows. So this
> would require backends doing significant numbers of row changes to either
> directly update pg_statistic or report their in progress numbers to the
> stats collector. The key change here is the partial execution numbers
> would need to be sent. Clearly one would need to avoid doing this too
> often (!) - possibly only when number of changed rows >
> autovacuum_analyze_scale_factor proportion of the relation concerned or
> similar.
Are you loading using COPY? Why not break down the load into chunks?
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
