Re: Why is plan (and performance) different on partitioned table?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mark Liberman" <mliberman(at)mixedsignals(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Why is plan (and performance) different on partitioned table?
Date: 2006-05-02 20:27:52
Message-ID: 26842.1146601672@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

"Mark Liberman" <mliberman(at)mixedsignals(dot)com> writes:
> Now, the potentital bug:
> It appears that after you truncate a table, the statistics for that =
> table still remain in pg_statistics.

That's intentional, on the theory that when the table is re-populated
the new contents will probably resemble the old.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Jim C. Nasby 2006-05-02 20:28:37 Re: Performance Issues on Opteron Dual Core
Previous Message Bruno Wolff III 2006-05-02 20:19:29 Re: postgresql transaction id monitoring with nagios