| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: last_analyze/last_vacuum not being updated |
| Date: | 2015-06-15 20:45:55 |
| Message-ID: | 557F3983.1060208@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/8/15 3:16 PM, Peter Eisentraut wrote:
> I'm looking at a case on 9.4.1 where the last_analyze and last_vacuum
> stats for a handful of tables seem stuck. They don't update after
> running an ANALYZE or VACUUM command, and they don't react to
> pg_stat_reset_single_table_counters(). All of the affected tables are
> system catalogs, some shared, some not. Other system catalogs and other
> tables have their statistics updated normally. Any ideas (before I try
> to blow it away)?
This issue somehow went away before I had time to analyze it further,
which is weird in itself. But now I have seen a segfault on a
completely different 9.4 instance while querying pg_stat_databases.
Could be bad luck. But if others are seeing weird stats collector
behavior in 9.4, please share.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2015-06-15 21:52:50 | Re: Function to get size of notification queue? |
| Previous Message | Robert Haas | 2015-06-15 20:38:28 | Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1 |