pgsql: Add a generic command progress reporting facility.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add a generic command progress reporting facility.
Date: 2016-03-09 17:16:59
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-committers

Add a generic command progress reporting facility.

Using this facility, any utility command can report the target relation
upon which it is operating, if there is one, and up to 10 64-bit
counters; the intent of this is that users should be able to figure out
what a utility command is doing without having to resort to ugly hacks
like attaching strace to a backend.

As a demonstration, this adds very crude reporting to lazy vacuum; we
just report the target relation and nothing else. A forthcoming patch
will make VACUUM report a bunch of additional data that will make this
much more interesting. But this gets the basic framework in place.

Vinayak Pokale, Rahila Syed, Amit Langote, Robert Haas, reviewed by
Kyotaro Horiguchi, Jim Nasby, Thom Brown, Masahiko Sawada, Fujii Masao,
and Masanori Oyama.



Modified Files
src/backend/access/transam/xact.c | 4 ++
src/backend/commands/vacuumlazy.c | 4 ++
src/backend/postmaster/pgstat.c | 73 +++++++++++++++++++++++++
src/backend/utils/adt/pgstatfuncs.c | 103 ++++++++++++++++++++++++++++++++++++
src/include/catalog/catversion.h | 2 +-
src/include/catalog/pg_proc.h | 2 +
src/include/pgstat.h | 30 +++++++++++
7 files changed, 217 insertions(+), 1 deletion(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Alvaro Herrera 2016-03-09 17:35:46 pgsql: pgcrypto: support changing S2K iteration count
Previous Message Tom Lane 2016-03-09 15:57:01 pgsql: Fix incorrect tlist generation in create_gather_plan().