| From: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
|---|---|
| To: | Luca Ferrari <fluca1978(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pg_stat_user_tables.n_tup_ins empty for partitioned table |
| Date: | 2019-05-24 07:26:13 |
| Message-ID: | CAKJS1f-VVpdBsVWTbCsDG0ZLPExhNidfGj3HmNeXgXbhv4=qVQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, 24 May 2019 at 19:20, Luca Ferrari <fluca1978(at)gmail(dot)com> wrote:
>
> On Wed, May 22, 2019 at 7:55 PM Andres Freund <andres(at)anarazel(dot)de> wrote:
> > That clearly seems wrong. Could you try build a small reproducer?
>
> Apparently not, I've tried to simulate the same but without any
> success, that is n_tup_ins is always correctly set.
> However, I've noted that this behavior applies up to february
Did you perhaps reset the stats or failover to a standby around Feb?
What does: select stats_Reset from pg_stat_database where datname =
current_database(); say?
--
David Rowley http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2019-05-24 08:05:01 | Re: pg_stat_user_tables.n_tup_ins empty for partitioned table |
| Previous Message | Luca Ferrari | 2019-05-24 07:19:51 | Re: pg_stat_user_tables.n_tup_ins empty for partitioned table |