"backend process" confused with "server process"

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: "backend process" confused with "server process"
Date: 2024-04-15 09:01:18
Message-ID: CACJufxEGKJXns06_usCizWEoP8fGg7KmOZYopBpq40wiO_txQQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

hi.

pg_log_backend_memory_contexts
we have
`
if (proc == NULL)
{
/*
* This is just a warning so a loop-through-resultset will not abort
* if one backend terminated on its own during the run.
*/
ereport(WARNING,
(errmsg("PID %d is not a PostgreSQL server process", pid)));
PG_RETURN_BOOL(false);
}
`

pg_signal_backend
`
if (proc == NULL)
{
/*
* This is just a warning so a loop-through-resultset will not abort
* if one backend terminated on its own during the run.
*/
ereport(WARNING,
(errmsg("PID %d is not a PostgreSQL backend process", pid)));

return SIGNAL_BACKEND_ERROR;
}
`

"is not a PostgreSQL server process" is the same thing as "not a
PostgreSQL backend process"?
should we unify it?

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2024-04-15 09:07:05 Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?
Previous Message Amit Kapila 2024-04-15 08:59:16 Re: promotion related handling in pg_sync_replication_slots()