Andreas Pflug wrote: > Bruce Momjian wrote: > > > > > This seems quite involved. Can we get the basic functionality I > > described first? > > On the way. > > > Also I am not sure how all this information is going > > to be passed from the logging process to the backend requesting the > > information, and it seems overly complicated. > > There's *no* information passing from the logging process, with the > single exception of the latest logfile timestamp (if allowed). I'd > rather like to have that information from the logger, to be safe in case > the system time was manipulated and the last logfile is not the current one. > The rest is just a reworked version of pg_dir_ls, with internal > knowledge of how the timestamp is formatted.
Oh, so you are hardcoding the logfile name so you can interpret the timestamp from that? It seems cleaner to allow the admin to specify whatever log pattern the want. However, you idea of expiring the log files based on timestamp values is pretty powerful. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
