On Thu, 2007-12-13 at 10:55 -0300, Alvaro Herrera wrote: > 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")
That was my first thought, but that ends up with the archiver ps display being mostly blank, and so isn't really very useful. -- Simon Riggs 2ndQuadrant http://www.2ndQuadrant.com ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
