pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Crash Recovery, pt 2
3+ messages / 2 participants
[nested] [flat]

* Crash Recovery, pt 2
@ 2003-01-24 14:12 Ron Johnson <ron.l.johnson@cox.net>
  2003-01-24 15:48 ` Re: Crash Recovery, pt 2 Andrew Sullivan <andrew@libertyrms.info>
  0 siblings, 1 reply; 3+ messages in thread

From: Ron Johnson @ 2003-01-24 14:12 UTC (permalink / raw)
  To: pgsql-performance

On Fri, 2003-01-24 at 07:22, Andrew Sullivan wrote:
> On Thu, Jan 23, 2003 at 10:32:58PM -0500, Noah Silverman wrote:
> > To preface my question, we are still in the process of evaluating postgres 
> > to determine if we want to switch our production environment over.
> > 
> > I'm curious about where I can find documentation about crash recovery in 
> > postgres.  In mysql, there is a nice table recovery utility (myisamchk). 
> 
> It recovers automatically.  Make sure you run with fsync turned on. 
> That calls fsync on the WAL at the point of every COMMIT, and COMMIT
> isn't finished before the fsync returns.  Then, in case of a crash,
> the WAL just plays back and fixes up the data area.

On commercial databases, there's a command to flush the roll-forward
logs to tape at intervals during the day.

Thus, if the disk(s) get corrupted, one can restore the database to
new disks, then apply the on-tape roll-forward logs to the database,
and you'd have only lost a few hours of data, instead of however
many hours (or days) it's been since the last database backup.

Also, flushing them to tape (or a different partition) ensures that
they don't fill up the partition during a particularly intensive
batch job.

Are there any FM's that explain how this works in Postgres?

Thanks,
Ron
-- 
+---------------------------------------------------------------+
| Ron Johnson, Jr.        mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA      http://members.cox.net/ron.l.johnson  |
|                                                               |
| "Fear the Penguin!!"                                          |
+---------------------------------------------------------------+




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Crash Recovery, pt 2
  2003-01-24 14:12 Crash Recovery, pt 2 Ron Johnson <ron.l.johnson@cox.net>
@ 2003-01-24 15:48 ` Andrew Sullivan <andrew@libertyrms.info>
  2003-01-24 18:46   ` Re: Crash Recovery, pt 2 Ron Johnson <ron.l.johnson@cox.net>
  0 siblings, 1 reply; 3+ messages in thread

From: Andrew Sullivan @ 2003-01-24 15:48 UTC (permalink / raw)
  To: pgsql-performance

On Fri, Jan 24, 2003 at 08:12:19AM -0600, Ron Johnson wrote:

> On commercial databases, there's a command to flush the roll-forward
> logs to tape at intervals during the day.

[. . .]

> Are there any FM's that explain how this works in Postgres?

Not yet, because you can't do it.

There is, I understand, some code currently being included in 7.4 to
do this.  So that's when it'll happen.  Look for "point in time
recovery" or "PITR" on the -hackers list to see the progress.

A

-- 
----
Andrew Sullivan                         204-4141 Yonge Street
Liberty RMS                           Toronto, Ontario Canada
<andrew@libertyrms.info>                              M2P 2A8
                                         +1 416 646 3304 x110




^ permalink  raw  reply  [nested|flat] 3+ messages in thread

* Re: Crash Recovery, pt 2
  2003-01-24 14:12 Crash Recovery, pt 2 Ron Johnson <ron.l.johnson@cox.net>
  2003-01-24 15:48 ` Re: Crash Recovery, pt 2 Andrew Sullivan <andrew@libertyrms.info>
@ 2003-01-24 18:46   ` Ron Johnson <ron.l.johnson@cox.net>
  0 siblings, 0 replies; 3+ messages in thread

From: Ron Johnson @ 2003-01-24 18:46 UTC (permalink / raw)
  To: pgsql-performance

On Fri, 2003-01-24 at 09:48, Andrew Sullivan wrote:
> On Fri, Jan 24, 2003 at 08:12:19AM -0600, Ron Johnson wrote:
> 
> > On commercial databases, there's a command to flush the roll-forward
> > logs to tape at intervals during the day.
> 
> [. . .]
> 
> > Are there any FM's that explain how this works in Postgres?
> 
> Not yet, because you can't do it.
> 
> There is, I understand, some code currently being included in 7.4 to
> do this.  So that's when it'll happen.  Look for "point in time
> recovery" or "PITR" on the -hackers list to see the progress.

Great!  That's a big step towards enterprise functiomality.

Another big step would be aggregate functions using indexes, but 
that's been discussed before...

-- 
+---------------------------------------------------------------+
| Ron Johnson, Jr.        mailto:ron.l.johnson@cox.net          |
| Jefferson, LA  USA      http://members.cox.net/ron.l.johnson  |
|                                                               |
| "Fear the Penguin!!"                                          |
+---------------------------------------------------------------+




^ permalink  raw  reply  [nested|flat] 3+ messages in thread


end of thread, other threads:[~2003-01-24 18:46 UTC | newest]

Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2003-01-24 14:12 Crash Recovery, pt 2 Ron Johnson <ron.l.johnson@cox.net>
2003-01-24 15:48 ` Andrew Sullivan <andrew@libertyrms.info>
2003-01-24 18:46   ` Ron Johnson <ron.l.johnson@cox.net>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox