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 ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
