Re: Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn
Date
Msg-id 11143.1473647903@sss.pgh.pa.us
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn  (Michael Paquier <michael.paquier@gmail.com>)
Re: Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Michael Paquier <michael.paquier@gmail.com> writes:
> Indeed, and the query field does not have much more meaning for a WAL
> sender. So I'd propose the attached for 9.6 and HEAD. I have thought
> about reporting that to pgstat in StartReplication(), but as there is
> some error handling there I'd think that WalSndLoop() is a better
> place to call pgstat_report_activity, as per the attached.

As long as it's a fixed string there's no reason to set it repeatedly,
so this placement looks fine for now.  We can reconsider when/if we
make it variable and decide what is going to drive it.

On reflection, maybe s/walsender/WAL sender/?  It doesn't look like
we really use the word "walsender" in user-facing docs.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Use LEFT JOINs in some system views in case referenced row doesn
Next
From: Michael Paquier
Date:
Subject: Re: Forbid use of LF and CR characters in database and role names