| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: Small TRUNCATE glitch |
| Date: | 2008-04-03 17:07:44 |
| Message-ID: | 4121.1207242464@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Martijn van Oosterhout <kleptog(at)svana(dot)org> writes:
> On Thu, Apr 03, 2008 at 11:58:11AM -0400, Tom Lane wrote:
>> Just noticed that TRUNCATE fails to clear the stats collector's counts
>> for the table. I am not sure if it should reset the event counts or
>> not (any thoughts?) but surely it is wrong to not zero the live/dead
>> tuple counts.
> Wern't there complaints from people regularly truncating and
> refilling tables getting bad plans because they lost the statistics?
Not related --- the planner doesn't look at pgstats data.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Svenne Krap | 2008-04-03 17:07:56 | Re: [GENERAL] SHA1 on postgres 8.3 |
| Previous Message | Bruce Momjian | 2008-04-03 17:06:49 | Re: psql \G command -- send query and output using extended format |