On Sun, 2006-04-16 at 15:22 +0100, Simon Riggs wrote: > On Sat, 2006-04-15 at 16:20 -0400, Bruce Momjian wrote: > > Simon Riggs wrote: > > > On Sat, 2006-04-15 at 12:24 -0400, Bruce Momjian wrote: > > > > And if we can't provide one, should we supply an SQL function > > > > to return the current WAL name? > > > > > > I'll do this. Just give me a few days to get my feet under the new desk. > > > I know its well past time I sorted this and a few other things out. > > > > If we get some mechanism to write those partial WAL files, we might not > > need the ability to identify the current WAL file, and because a new > > function is going to require an initdb, I am thinking we can't get this > > done until 8.2 anyway, so Simon, please come up with a plan to finish > > the missing PITR pieces. I am getting tired of trying to explain > > workarounds to PITR users, especially when the workarounds are not easy.
> For 8.0. and 8.1 users, I'd suggest we release an external function as a > contrib module, so that we don't compromise reliability and not force an > initdb for them. With docs, of course. > > I suggest we have two functions: > 1. pg_xlog_file_from_offset(text) > This allows the output of pg_stop_backup to be formatted into a > filename, so it would be used like this: > select pg_xlog_file_from_offset(pg_stop_backup()); Patch to implement this as a contrib module enclosed. No main manual doc patch yet, awaiting review. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
Description: Unix tar archive
---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org