Skip site navigation (1) Skip section navigation (2)

Re: PostgreSQL - Debian - Processes: postgres: writer process, etc.

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: PostgreSQL - Debian - Processes: postgres: writer process, etc.
Date: 2012-02-14 17:16:18
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-novice
On Mon, Jan 30, 2012 at 11:05:10AM -0500, Tom Lane wrote:
> >> 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.)

I belive the 'c' command in modern versions of top toggles display of
the current command string.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + It's impossible for everything to be true. +

In response to


pgsql-novice by date

Next:From: Bruce MomjianDate: 2012-02-14 21:23:39
Subject: Re: Using libpq 8.4 with PostgreSQL 9.1
Previous:From: Merlin MoncureDate: 2012-02-14 14:43:48
Subject: Re: insert fail gracefully if primary key already exists

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group