Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] Reporting xmin from VACUUMs - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Reporting xmin from VACUUMs
Date
Msg-id CA+TgmoaN7nW+Bfd93j2sD_XAVqoT8ZUPAv09Za1_M+9b_Wu7Eg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Reporting xmin from VACUUMs  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: [HACKERS] Reporting xmin from VACUUMs  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Re: [HACKERS] Reporting xmin from VACUUMs  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
Tree view 
On Fri, Feb 10, 2017 at 3:30 AM, Simon Riggs <simon@2ndquadrant.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.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)
Next
From: Corey Huinker
Date:
Subject: Re: \if, \elseif, \else, \endif (was Re: [HACKERS] PSQL commands:\quit_if, \quit_unless)