Re: [Fwd: [PATCHES] archiver ps display]

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [Fwd: [PATCHES] archiver ps display]
Date: 2007-12-13 13:55:00
Message-ID: 20071213135500.GH6262@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs wrote:
>
> Now that we have set archiver messages to DEBUG levels, there's no easy
> way of seeing what file we are currently working on.
>
> The behaviour of the startup process and archiver should be symmetrical,
> allowing it to be used for replication monitoring.
>
> Before archive_command
> postgres: archiver process archiving 00000001000000000000000B
>
> After archive_command
> postgres: archiver process archived 00000001000000000000000B

I agree that replication should be able to be monitored. However,
isn't ps_display supposed to show what the process is _currently_ doing?
So if the archiver finishes processing a file, its display should go
back to "idle" or some such. (Perhaps "idle, last archived XXXYYYZZZ")

--
Alvaro Herrera http://www.amazon.com/gp/registry/5ZYLFMCVHXC
"After a quick R of TFM, all I can say is HOLY CR** THAT IS COOL! PostgreSQL was
amazing when I first started using it at 7.2, and I'm continually astounded by
learning new features and techniques made available by the continuing work of
the development team."
Berend Tober, http://archives.postgresql.org/pgsql-hackers/2007-08/msg01009.php

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2007-12-13 14:16:14 Re: [Fwd: [PATCHES] archiver ps display]
Previous Message Alvaro Herrera 2007-12-13 13:31:19 Re: [GENERAL] Slow PITR restore