pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Rod Taylor <rbt@rbt.ca>
To: Carlos Moreno <moreno@mochima.com>
Cc: PgSQL Performance ML <pgsql-performance@postgresql.org>
Subject: Re: Having trouble with backups (was: Re: Crash Recovery)
Date: 24 Jan 2003 11:08:55 -0500
Message-ID: <1043424535.58142.65.camel@jester> (raw)
In-Reply-To: <3E3158DA.7080807@mochima.com>
References: <2147483647.1043361178@[10.0.1.133]>
	<1043416377.29437.70.camel@haggis>
	<3E3158DA.7080807@mochima.com>

On Fri, 2003-01-24 at 10:16, Carlos Moreno wrote:
> Speaking about daily backups...  We are running into some serious
> trouble with our backup policy.
> 
> First (and less important), the size of our backups is increasing
> a lot;  yet information is not changing, only being added;  so, the
> obvious question:  is there a way to make incremental backup?

Incremental backups are coming. Some folks at RedHat are working on
finishing a PIT implementation, with with any luck 7.4 will do what you
want.

For the time being you might be able to cheat.  If you're not touching
the old data, it should come out in roughly the same order every time.

You might be able to get away with doing a diff between the new backup
and an older one, and simply store that. When restoring, you'll need to
patch together the proper restore file.

> And the second (and intriguing) problem:  whenever I run pg_dump,
> my system *freezes* until pg_dump finishes.  When I say "system",

No, this isn't normal -- nor do I believe it. The only explanation would
be a hardware or operating system limitation. I.e. with heavy disk usage
it used to be possible to peg the CPU -- making everything else CPU
starved, but the advent of DMA drives put an end to that.

A pg_dump is not resource friendly, simply due to the quantity of
information its dealing with. Are you dumping across a network? Perhaps
the NIC is maxed out.

-- 
Rod Taylor <rbt@rbt.ca>

PGP Key: http://www.rbt.ca/rbtpub.asc

Attachments:

  signature.asc (application/pgp-signature, 186B) download

view thread (13+ messages)  latest in thread

Message-ID: <1043424535.58142.65.camel@jester>
Permalink:  ../1043424535.58142.65.camel@jester/
Also on:    postgresql.org/message-id/1043424535.58142.65.camel@jester

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-performance@postgresql.org
  Cc: rbt@rbt.ca, moreno@mochima.com
  Subject: Re: Having trouble with backups (was: Re: Crash Recovery)
  In-Reply-To: <1043424535.58142.65.camel@jester>
  References: <2147483647.1043361178@[10.0.1.133]> <1043416377.29437.70.camel@haggis> <3E3158DA.7080807@mochima.com> <1043424535.58142.65.camel@jester>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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