Re: PostgreSQL - Debian - Processes: postgres: writer process, etc.
От | Tom Lane |
---|---|
Тема | Re: PostgreSQL - Debian - Processes: postgres: writer process, etc. |
Дата | |
Msg-id | 15390.1327939510@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: PostgreSQL - Debian - Processes: postgres: writer process, etc. ("Jean-Yves F. Barbier" <12ukwn@gmail.com>) |
Ответы |
Re: PostgreSQL - Debian - Processes: postgres: writer process, etc.
Re: PostgreSQL - Debian - Processes: postgres: writer process, etc. |
Список | pgsql-novice |
"Jean-Yves F. Barbier" <12ukwn@gmail.com> writes: > On Mon, 30 Jan 2012 02:24:08 -0800 (PST) > Windybell <lmhelp1@orange.fr> wrote: >> I am wondering what are these four last processes ("postgres: writer", >> "postgres: wal writer", "postgres: autovacuum launcher" and "postgres: stats >> collector")? > Because, as their name suggest it, they take care of Pg different > parts. Right. >> Their PPID is 3069. > That can't be, each running software/process have a different PID. > This PID Nb is in the 2nd column. He said PPID, that is *parent* process ID, so the above is expected --- they should all be children of the same postmaster process. >> What is weird to me is the "COMMAND" column as far as these four processes >> are concerned. >> In the "COMMAND "column I would expect a real command, not a description. >> Can you explain? We intentionally change the command string reported by ps for each postmaster child process, so that you can tell the various processes apart. If we did not, every postmaster child would show the exact same command string as the postmaster itself was launched with. (To get an idea of how useless that is, try looking at "top" sometime --- on most systems I've worked with, it ignores the changed command strings, so you can't tell what's what.) regards, tom lane
В списке pgsql-novice по дате отправления: