Re: pgsql: Allow vacuums to report oldestxmin

Masahiko Sawada <sawada.mshk@gmail.com>

View thread View on postgr.es

From: Masahiko Sawada <sawada.mshk@gmail.com>

To: Simon Riggs <simon@2ndquadrant.com>

Cc: pgsql-committers@postgresql.org, PostgreSQL-development <pgsql-hackers@postgresql.org>

Date: 2017-03-06T12:37:58Z

Lists: pgsql-hackers

Attachments

fix_vacuum_example_in_doc.patch (application/octet-stream) patch

On Fri, Mar 3, 2017 at 10:50 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> Allow vacuums to report oldestxmin
>
> Allow VACUUM and Autovacuum to report the oldestxmin value they
> used while cleaning tables, helping to make better sense out of
> the other statistics we report in various cases.
>
> Branch
> ------
> master
>
> Details
> -------
> http://git.postgresql.org/pg/commitdiff/9eb344faf54a849898d9be012ddfa8204cfeb57c
>
> Modified Files
> --------------
> src/backend/commands/vacuumlazy.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
>

Should we change the example in vacuum.sgml file as well? Attached patch.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Commits

Simplify the example of VACUUM in documentation.
- 75eea8d7f54b 9.2.21 landed
- 82f7c3255300 9.3.17 landed
- cb366b507995 9.4.12 landed
- 86f0e538955e 9.5.7 landed
- fa0d1fd8955c 9.6.3 landed
- ec19693014ed 10.0 landed
Allow vacuums to report oldestxmin
- 9eb344faf54a 10.0 cited
Message editing: remove gratuitous variations in message wording, standardize
- feb4f44d296b 7.4.1 cited