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. We added PITR in 8.0, and we have made little improvement to it since then, and its limitations are getting tiring. -- Bruce Momjian http://candle.pha.pa.us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. + ---------------------------(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
