From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Reporting xmin from VACUUMs |
Date: | 2017-02-19 22:31:06 |
Message-ID: | 6626c64d-705d-47b1-f7d6-3995a3a22630@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2/19/17 3:43 AM, Robert Haas wrote:
> This is the kind of information that you really want to see once per
> autovac, though, not just the most recent autovac or some kind of
> cumulative total. Knowing that I've done 301 index scans in my last
> 300 vacuums is not nearly as useful as knowing which autovacuum did 2
> index scans and what exactly was going on with that vacuum. So I'm
> not sure including this sort of thing in the stats files would be very
> useful, or at least you'd want to think carefully about how to do it.
Well, counters would be better than nothing I think, but I agree with
your concern. Really, that's a problem for the entire stats system to
varying degrees.
> As far as bloating the stats file is concerned, the big problem there
> is that our current design for the stats file requires rewriting the
> entire thing any time we want to update even a single byte of data.
> We could fix that by splitting up the files more so that they are
> smaller and faster to rewrite, but we could also fix it by coming up
> with a way of rewriting just one part of a file instead of the whole
> thing, or we could think about storing it in DSM so that you don't
> have to rewrite anything at all. I think that last option is worth
> some serious study now that we have DSA, but it's currently not very
> high on my personal priority list.
Hmm... so basically replace the temporary file with DSM?
Something else I think would be useful is a way to subscribe to stats
updates.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
From | Date | Subject | |
---|---|---|---|
Next Message | neha khatri | 2017-02-19 22:34:02 | Resolved typo in a comment |
Previous Message | Erik Rijkers | 2017-02-19 22:27:00 | Re: Logical replication existing data copy - comments snapbuild.c |