Andreas Pflug wrote: > > OK, it would be nice if we could do a sed operation like: > > > > sed 's/%./*/g' > > > > but I don't know a way to do that without defining a function or pulling > > in a procedural language, but if we could do it we could do: > > > > pg_dir(echo log_destination | sed 's/%./*/g') > > > > Argggg.... ever used sed on win32?!? And how should the timestamp be > represented in client tools? Date/time interpretation is always a source > of problems, so *please* let the server do that.
I am thinking of these all being server-side functions. > Rethinking all this, I'd like the pg_logfile_list to return a complex type: > > CREATE TYPE pg_logfile_list AS ( > filedate timestamp, > filename text, > backendpid int, > inuse bool) > > and > > pg_logfile_list() RETURNS SETOF pg_logfile_list > > which would enable > > SELECT filename, > pg_file_unlink(filename) > FROM pg_logfile_list() > WHERE filedate < current_timestamp - '3 months'::interval > AND NOT inuse > > In-use check is easy for the backend, if the syslog process publishes > the current logfile's timestamp in sharedmem. > > We can use a GUC variable for the log_directory (not log_destination); > anyway, I'd like the filenames to be selected by the server. This seems quite involved. Can we get the basic functionality I described first? 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. -- 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])
