[MASSMAIL]"backend process" confused with "server process" - Mailing list pgsql-hackers

From jian he
Subject [MASSMAIL]"backend process" confused with "server process"
Date
Msg-id CACJufxEGKJXns06_usCizWEoP8fGg7KmOZYopBpq40wiO_txQQ@mail.gmail.com
Whole thread Raw
Responses Re: "backend process" confused with "server process"  ("Andrey M. Borodin" <x4mmm@yandex-team.ru>)
List 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?



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: promotion related handling in pg_sync_replication_slots()
Next
From: Daniel Gustafsson
Date:
Subject: Re: Cutting support for OpenSSL 1.0.1 and 1.0.2 in 17~?