Re: BUG #8681: column 'n_tup_del' of pg_stat_user_tables doesn't change in case of truncate

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rod Taylor <rod(dot)taylor(at)gmail(dot)com>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Anit Chakkarwar <anitchakkarwar(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #8681: column 'n_tup_del' of pg_stat_user_tables doesn't change in case of truncate
Date: 2013-12-17 00:17:08
Message-ID: 18896.1387239428@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Rod Taylor <rod(dot)taylor(at)gmail(dot)com> writes:
> Why doesn't truncate reset table statistic to 0?

Well, it does reset the counts that correspond to current table size.
This one doesn't though. n_tup_del is a count of historical operations.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2013-12-17 00:18:42 Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs
Previous Message Sergey Konoplev 2013-12-16 23:18:14 Re: [BUG] Segmentation fault in pfree in PLy_output_tuple_funcs