Yes, we need point-in-time recovery. We don't have that yet. It is on
the TODO list.
---------------------------------------------------------------------------
Andy Marden wrote:
> Does no one consider this to be a problem? You kinda wonder about PostgreSQL
> being used as serious commercial database then don't you?
>
> Me again.
>
> "Andy Marden" <amarden@usa.net> wrote in message
> news:a3dpjt$1l1s$1@news.tht.net...
> > Putting together a system at the moment with a combination of batch loads
> > and user online modification of data, with PostgreSQL version 7.1.3. I'm
> > looking at recovery aspects at the moment. All I can see is pg_dump and
> > pg_restore at the moment, which is fine for batch loads once a day, but if
> > the database crashes halfway through the day then user modifications will
> be
> > lost.
> >
> > Is there the equivalent of Oracle's archived redo logs in PostgreSQL and
> > commands to allow recovery up to the last (or any) point in time. I've
> seen
> > pg_xlog files mentioned.
> >
> > The recovery section of the manuals is 'under construction' it seems.
> >
> > Thanks for your help.
> >
> > Cheers
> >
> > Andy Marden
> >
> >
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
>
> http://www.postgresql.org/users-lounge/docs/faq.html
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026