Re: Reporting xmin from VACUUMs

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reporting xmin from VACUUMs
Date: 2017-02-10 22:18:28
Message-ID: 20170210221828.jj2jnuwk4zxv7boq@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas wrote:
> On Fri, Feb 10, 2017 at 3:30 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> 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 something like this. We already report
> a lot of other fine details, so what's one more? And it could be
> useful.

Yeah, I can see how this can be useful to debug some hard-to-track
problems. The patch looks sensible to me.

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2017-02-10 23:06:37 Re: WIP: About CMake v2
Previous Message Corey Huinker 2017-02-10 22:09:44 Re: \if, \elseif, \else, \endif (was Re: PSQL commands: \quit_if, \quit_unless)