| From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
|---|---|
| To: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: n_mod_since_analyze isn't reset at table truncation |
| Date: | 2021-03-04 03:21:14 |
| Message-ID: | a783f63a-dfba-7193-d58c-b24d0643e359@oss.nttdata.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2021/03/04 11:24, Julien Rouhaud wrote:
> On Thu, Mar 04, 2021 at 10:35:19AM +0900, Masahiko Sawada wrote:
>>
>> While reviewing "autoanalyze on partitioned table" patch, I realized
>> that pg_stat_xxx_tables.n_mod_since_analyze is not reset at TRUNCATE.
>> On the other hand, n_ins_since_vacuum is reset. I think it should be
>> reset because otherwise we end up unnecessarily triggering autoanalyze
>> even when the actual number of newly inserted tuples is less than the
>> autoanalyze thresholds.
In that case, conversely, we want to trigger autoanalyze ASAP because the contents in the table was changed very much?
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-03-04 03:33:02 | Re: Parallel INSERT (INTO ... SELECT ...) |
| Previous Message | tsunakawa.takay@fujitsu.com | 2021-03-04 02:52:11 | RE: Avoid CommandCounterIncrement in RI trigger when INSERT INTO referencing table |