From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Should rename "startup process" to something else? |
Date: | 2021-11-18 19:06:38 |
Message-ID: | CA+TgmoZTA-_e9jYkwFexKewKX+-H0cE1yexmYX_+9U3WypTW8A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Nov 18, 2021 at 12:24 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Being hackers ourselves, I'm not sure we're qualified to opine on
> that. I cannot say that I've noticed any questions about it on
> the mailing lists, though.
What I've noticed when supporting EDB customer is that if, say,
there's a problem with recovery, and they're trying to figure out
which process is responsible, they have no intuition that the startup
process is the likely culprit. They could, for example, notice whether
the LSN that shows up in the ps status is advancing over time. Or,
they could notice whether that process is doing a lot of I/O, or a lot
of CPU. But since they have no notion that a startup process has
anything to do with recovery, they don't make that connection. Now you
can argue that I ought to be happy about that because, hey, it's job
security. And you can also argue that even if the process had a better
name, a lot of people wouldn't figure it out for one reason or
another. However, my view is that we do well to make things more
comprehensible when we can.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2021-11-18 19:11:52 | Re: Should rename "startup process" to something else? |
Previous Message | Jeff Davis | 2021-11-18 18:50:29 | Re: Non-superuser subscription owners |