Horton

Re: exposing wait events for non-backends (was: Tracking wait event for latches)

Andres Freund <andres@anarazel.de>

View thread View on postgr.es
From: Andres Freund <andres@anarazel.de>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: Kuntal Ghosh <kuntalghosh.2007@gmail.com>, Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>, Michael Paquier <michael.paquier@gmail.com>, Robert Haas <robertmhaas@gmail.com>, Craig Ringer <craig@2ndquadrant.com>, Kevin Grittner <kgrittn@gmail.com>, Alvaro Herrera <alvherre@2ndquadrant.com>, Thomas Munro <thomas.munro@enterprisedb.com>, Alexander Korotkov <a.korotkov@postgrespro.ru>, PostgreSQL mailing lists <pgsql-hackers@postgresql.org>
Date: 2017-03-09T21:03:36Z
Lists: pgsql-hackers 
Hi,

On 2017-03-09 14:30:21 -0500, Peter Eisentraut wrote:
> In practice, I think it's common to do a quick select * from
> pg_stat_activity to determine whether a database instance is in use.

> (You always see your own session, but that's easy to eyeball.)  If we
> add all the various background processes by default, that will make
> things harder, especially if there is no straightforward way to filter
> them out.

A good chunk of those still apply to database attached background
workers (say dropping a database, using it as a template) - so I'm not
really convinced that's an issue.

- Andres

Commits

  1. Show more processes in pg_stat_activity.