diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-16 21:06:50 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2020-09-16 21:06:50 -0400 |
| commit | babef40c9a999949abe0ae8e82240cac3f154237 (patch) | |
| tree | 1d01029806233725a156c2a3cd66171525db6edd /src/backend/access/gist/gistvalidate.c | |
| parent | add105840b673ab3949abc2568da0d4f2fd496c5 (diff) | |
| download | postgresql-babef40c9a999949abe0ae8e82240cac3f154237.tar.gz | |
Teach walsender to update its process title for replication commands.
Because the code path taken for SQL commands executed in a walsender
will update the process title, we pretty much have to update the
title for replication commands as well. Otherwise, the title shows
"idle" for the rest of a logical walsender's lifetime once it's
executed any SQL command.
Playing with this, I confirm that a walsender now typically spends
most of its life reporting
walsender postgres [local] START_REPLICATION
Considering this in isolation, it might be better to have it say
walsender postgres [local] sending replication data
However, consistency with the other cases seems to be a stronger
argument.
In passing, remove duplicative pgstat_report_activity call.
Discussion: https://postgr.es/m/880181.1600026471@sss.pgh.pa.us
Diffstat (limited to 'src/backend/access/gist/gistvalidate.c')
0 files changed, 0 insertions, 0 deletions