Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-19 Thread Jim Nasby
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

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-19 Thread Robert Haas
On Sat, Feb 18, 2017 at 12:30 AM, Jim Nasby wrote: >> What? > > There's a bunch of information reported by vacuum logging but not in > pg_stat*, such as all-visible/frozen skipping, unable to get cleanup lock, > last freeze scan, times autovac has been interrupted.

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-17 Thread Jim Nasby
On 2/15/17 12:05 PM, Alvaro Herrera wrote: Jim Nasby wrote: ISTR previous discussion of allowing more stats files; if that happened I think having stats that were dedicated to (auto)vacuum would be very useful. That's clearly a lot more work though. What? There's a bunch of information

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-15 Thread Alvaro Herrera
Jim Nasby wrote: > ISTR previous discussion of allowing more stats files; if that happened > I think having stats that were dedicated to (auto)vacuum would be very > useful. That's clearly a lot more work though. What? -- Álvaro Herrerahttps://www.2ndQuadrant.com/ PostgreSQL

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-15 Thread Jim Nasby
Accidentally sent o--list. On 2/14/17 12:57 PM, Jim Nasby wrote: On 2/13/17 12:36 AM, Masahiko Sawada wrote: It seems sensible to me to do something like this. We already report a lot of other fine details, so what's one more? And it could be useful. Also, I've been proposing to report the

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-12 Thread Masahiko Sawada
On Sat, Feb 11, 2017 at 7:00 AM, Robert Haas wrote: > On Fri, Feb 10, 2017 at 3:30 AM, Simon Riggs wrote: >> We've added xmin info to pg_stat_activity and pg_stat_replication, but >> VACUUM doesn't yet report which xmin value it used when it ran. >>

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-10 Thread Alvaro Herrera
Robert Haas wrote: > On Fri, Feb 10, 2017 at 3:30 AM, Simon Riggs wrote: > > We've added xmin info to pg_stat_activity and pg_stat_replication, but > > VACUUM doesn't yet report which xmin value it used when it ran. > > > > Small patch to add this info to VACUUM output. >

Re: [HACKERS] Reporting xmin from VACUUMs

2017-02-10 Thread Robert Haas
On Fri, Feb 10, 2017 at 3:30 AM, Simon Riggs wrote: > We've added xmin info to pg_stat_activity and pg_stat_replication, but > VACUUM doesn't yet report which xmin value it used when it ran. > > Small patch to add this info to VACUUM output. It seems sensible to me to do

[HACKERS] Reporting xmin from VACUUMs

2017-02-10 Thread Simon Riggs
We've added xmin info to pg_stat_activity and pg_stat_replication, but VACUUM doesn't yet report which xmin value it used when it ran. Small patch to add this info to VACUUM output. -- Simon Riggshttp://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA,