Re: Small TRUNCATE glitch

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: Small TRUNCATE glitch
Date: 2008-04-03 22:13:53
Message-ID: 20080403221353.GP2528@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

Agreed, the live/dead counters should be reset. Regarding event counts,
my take is that we should have a separate statement count for truncate
(obviously not a tuple count), and the others should be left alone.

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2008-04-03 22:21:57 Re: psql \G command -- send query and output using extended format
Previous Message Alvaro Herrera 2008-04-03 22:11:17 Re: psql \G command -- send query and output using extended format