Re: incoherent dead tuples between pg_stat_user_tables and pgstattuple?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Luca Ferrari <fluca1978(at)gmail(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: incoherent dead tuples between pg_stat_user_tables and pgstattuple?
Date: 2019-09-27 14:43:03
Message-ID: 30297.1569595383@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Luca Ferrari <fluca1978(at)gmail(dot)com> writes:
> On Fri, Sep 27, 2019 at 3:52 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> n_live_tup/n_dead_tup should not be thought to be better than
>> approximations. Most operations adjust them only incrementally,
>> and messages to the stats collector can get dropped entirely
>> under heavy load, causing deltas to go missing. There are
>> also race conditions involved in some update scenarios.

> Are you suggesting tha autovacuum made free space available so that
> pg_stat_user_tables lags behind? Because I don't see last_autovacuum
> changing in the mantime.

I'm not suggesting any specific scenario, because you haven't presented
any evidence as to when those counts became off. I'm just saying that
there are plenty of possible mechanisms for them to become so.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Marco Ippolito 2019-09-27 15:10:52 Re: "Failed to connect to Postgres database"
Previous Message Adrian Klaver 2019-09-27 14:38:07 Re: "Failed to connect to Postgres database"