"Carlo Stonebanks" <stonec.register@xxxxxxxxxxxx> wrote: > Already done in an earlier post Perhaps I misunderstood; I thought that post mentioned that the plan was one statement in an iteration, and that the cache would have been primed by a previous query checking whether there were any rows to update. If that was the case, it might be worthwhile to look at the entire flow of an iteration. Also, if you ever responded with version and configuration information, I missed it. The solution to parts of what you describe would be different in different versions. In particular, you might be able to solve checkpoint-related lockup issues and then improve performance by using bigger batches. Right now I would be guessing at what might work for you. -Kevin -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
