Recovery - transaction logs 
Author Message
 Recovery - transaction logs

Yes, we need point-in-time recovery.  We don't have that yet.  It is on
the TODO list.

---------------------------------------------------------------------------

Quote:

> 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.



> > 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.***.com/

--
  Bruce Momjian                        |   http://www.***.com/

  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster



Sun, 25 Jul 2004 20:01:36 GMT
 Recovery - transaction logs

Let me be more specific.  We have redo logs in WAL that handle a case of
the system crashing during the day.  That is handled automatically.

What we don't have is a way to recover from a disk failure in the middle
of the day.  For that, we will need point-in-time recovery.

I am starting a data recovery article this week which should cover these
options.

---------------------------------------------------------------------------

Quote:

> 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.



> > 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

  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html



Sun, 25 Jul 2004 20:20:54 GMT
 Recovery - transaction logs

Actually, we do consider this to be a problem. From what I am hearing, they
are close to having some sort of point in time recovery.

An option to consider, i'm quite sure if we threw some money the developers
way, they might be persuaded.


Quote:
>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.



> > 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

--
Naomi Walker
Chief Information Officer
Eldorado Computing, Inc.
602-604-3100  ext 242

---------------------------(end of broadcast)---------------------------



Mon, 26 Jul 2004 03:24:13 GMT
 Recovery - transaction logs

Quote:


> >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

  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster



Mon, 26 Jul 2004 15:23:46 GMT
 Recovery - transaction logs
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

Quote:
----- Original Message -----




Sent: Thursday, February 07, 2002 7:12 AM
Subject: Re: [ADMIN] Recovery - transaction logs



> > >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

>   +  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

message can get through to the mailing list cleanly



Mon, 26 Jul 2004 17:41:34 GMT
 Recovery - transaction logs

Quote:

> 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.

I totally agree.  That's why it is under URGENT on the TODO list.

--
  Bruce Momjian                        |  http://candle.pha.pa.us

  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026

---------------------------(end of broadcast)---------------------------



Tue, 27 Jul 2004 01:20:43 GMT
 
 [ 6 post ] 

 Relevant Pages 

1. Recovery - transaction logs

2. Recovery of lost transaction logs on SQL7

3. Recovery of Records using Transaction Log

4. Restoring Transaction Logs -Point-in-time recovery is inhibited

5. Full Recovery Mode and Physical Size of Transaction Log

6. disater database recovery without transaction log

7. Transaction log growing with SIMPLE recovery

8. Database Recovery Using transaction Log.

9. Sql 2000 simple recovery mode transaction log full

10. DTS, Transaction Log, Simple Recovery

11. Recovery of database after transaction log destroyed

12. Transaction Log Growth vs. Recovery Model


 
Powered by phpBB® Forum Software