Received: from sunpine.krs.ru (SunPine.krs.ru [195.161.16.37]) by hub.org (8.9.3/8.9.3) with ESMTP id BAA76655 for ; Sat, 11 Sep 1999 01:45:22 -0400 (EDT) (envelope-from vadim@krs.ru) Received: from krs.ru (dune.krs.ru [195.161.16.38]) by sunpine.krs.ru (8.8.8/8.8.8) with ESMTP id NAA01036; Sat, 11 Sep 1999 13:45:14 +0800 (KRSS) Sender: root@sunpine.krs.ru Message-ID: <37D9EC69.8FC94FB0@krs.ru> Date: Sat, 11 Sep 1999 13:45:13 +0800 From: Vadim Mikheev Organization: OJSC Rostelecom (Krasnoyarsk) X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Wayne Piekarski CC: pgsql-sql@postgreSQL.org Subject: Re: [SQL] Fast Backups With pg_dump References: <199909110513.OAA15799@helpdesk.senet.com.au> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Wayne Piekarski wrote: > > Currently, I am running the pg_dump program every hour to produce backups > of the database, and then storing them in case something fails or I need > recover something. > > However, the backups are quite large, and the CPU gets really thrashed a > lot doing the COPY as it has to make lots of function calls (as mentioned > in a previous email of mine to hackers) and I wanted to avoid this if > possible. > > What would be really neat is if you could do something like, give me a > dump of all rows changed since the last backup, sortof like a diff file, > so I make a full backup at the start of the day, and then just store > deltas for the rest of the day. I know that postgres can keep track of > this kind of stuff because the MVCC allows it to make a consistent > snapshot of the dbms even while updates are occuring, so is this kind of > idea possible (or does it already exist?) I implement transaction logging for 6.6 - you will be able to do incremental backup by copying log file. Vadim