On Wed, Dec 28, 2016 at 11:57 AM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > But I'm starting to think that the best way might be to do BOTH of the > things I said in my previous message: make dsa.c register on > create/attach and also unregister before detaching iff the name was > supplied at creation time for the benefit of extension writers, but > make it not do anything at all about tranche name > registration/unregistration if NULL was passed in at create time. > Then register this particular tranche (LWTRANCHE_PARALLEL_QUERY_DSA) > in every process in RegisterLWLockTranches. That way, you'd get a > useful name in pg_stat_activity for other backends that are running > parallel queries if they are ever waiting for these locks (unlikely > but interesting to know abotu if it happens).
Maybe something like the attached. -- Thomas Munro http://www.enterprisedb.com
fix-dsa-tranche-registration.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
