Re: Rapidly decaying performance repopulating a large table

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Greg Smith <gsmith(at)gregsmith(dot)com>
Cc: David Wilson <david(dot)t(dot)wilson(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Rapidly decaying performance repopulating a large table
Date: 2008-04-23 06:29:42
Message-ID: 3109.1208932182@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Greg Smith <gsmith(at)gregsmith(dot)com> writes:
> ...This is a bit out of my area, but after reading the rest of this thread I
> wonder whether raising the default_statistics_target parameter a bit might
> reduce the instances of bad plans showing up.

On the evidence so far, it doesn't seem that David's problem has
anything to do with bad plans --- I suspected that at first, but the
theory's been shot down. I'm now thinking it's an I/O bottleneck in
some form ...

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Michael Fuhr 2008-04-23 07:04:53 Re: Postgres Encoding conversion problem
Previous Message Greg Smith 2008-04-23 05:59:23 Re: Rapidly decaying performance repopulating a large table