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

2007-12-13 Thread Simon Riggs
On Thu, 2007-12-13 at 15:58 +0100, Peter Eisentraut wrote: > Am Donnerstag, 13. Dezember 2007 schrieb Simon Riggs: > > Now that we have set archiver messages to DEBUG levels, there's no easy > > way of seeing what file we are currently working on. > > > After archive_command > > postgres: archiver

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

2007-12-13 Thread Peter Eisentraut
Am Donnerstag, 13. Dezember 2007 schrieb Simon Riggs: > Now that we have set archiver messages to DEBUG levels, there's no easy > way of seeing what file we are currently working on. > After archive_command > postgres: archiver process archived 0001000B ps isn't a very robust an

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

2007-12-13 Thread Simon Riggs
On Thu, 2007-12-13 at 11:16 -0300, Alvaro Herrera wrote: > Simon Riggs wrote: > > On Thu, 2007-12-13 at 10:55 -0300, Alvaro Herrera wrote: > > > > I agree that replication should be able to be monitored. However, > > > isn't ps_display supposed to show what the process is _currently_ doing? > > >

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

2007-12-13 Thread Alvaro Herrera
Simon Riggs wrote: > On Thu, 2007-12-13 at 10:55 -0300, Alvaro Herrera wrote: > > 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

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

2007-12-13 Thread Simon Riggs
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, >

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

2007-12-13 Thread Alvaro Herrera
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 archi

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

2007-12-13 Thread Simon Riggs
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 proce