+1 On Tue, Jun 20, 2017 at 8:54 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote: > Unless you have a lot of users running psql manually, I don't see how > this is actually very useful or actionable. What would the user do with > the information? Hopefully your users already trust that you'd keep the > downtime to the minimum possible.
I think this feature would be useful for PgTerminator (https://github.com/trustly/pgterminator) a tool which automatically kills unprotected processes that could potentially be the reason why >X number of protected important processes have been waiting for >Y seconds. When I'm guilty of locking this in the production DB and get killed by PgTerminator, it would be nice to know the reason, e.g. that it was PgTerminator that killed me and what process I was blocking. -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers