Re: [COMMITTERS] pgsql: Fix possible crash reading pg_stat_activity.

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> No, I think backend-lifetime is right. The tranche registrations are
> all backend-local state, so there's no problem with backend A
> registering a string at one address and backend B registering a string
> at a different address. It's just important that neither of those
> strings goes away before the corresponding backend does.

Then I don't understand what's going on. Isn't the crash you fixed
because backend A was looking at the tranche containing the lock backend B
was blocked on? How can a tranche name local to backend B work?

regards, tom lane