I'm just coming at this from the point of view of someone who's implementing PostgreSQL for the first time, but has in-depth Oracle experience. This is the one area left where organisations are going to discount PostgreSQL because they can't afford to tell people that all data entered that day has to be re-entered (sorry) because of a database corruption. How slick it is doesn't matter initially, as long as it can reliably be done.
Andy ----- Original Message ----- From: "Bruce Momjian" <[EMAIL PROTECTED]> To: "Chad R. Larson" <[EMAIL PROTECTED]> Cc: "Andy Marden" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Thursday, February 07, 2002 7:12 AM Subject: Re: [ADMIN] Recovery - transaction logs > Chad R. Larson wrote: > > At 06:59 AM 2/6/02 -0500, Bruce Momjian wrote: > > >Yes, we need point-in-time recovery. We don't have that yet. It is on > > >the TODO list. > > > > How's the status on that? Around a year ago, it was predicted to be in > > 7.1.3, or 7.2 at the latest. How now? > > No one has worked on it. Sorry. > > -- > Bruce Momjian | http://candle.pha.pa.us > [EMAIL PROTECTED] | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 > ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly