Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id D018D64FCFB for ; Wed, 15 Oct 2008 07:31:22 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 92761-10 for ; Wed, 15 Oct 2008 07:31:16 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by postgresql.org (Postfix) with ESMTP id 856FF64FE8F for ; Wed, 15 Oct 2008 07:31:13 -0300 (ADT) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Kq3eo-0001HP-Hy for pgsql-performance@postgresql.org; Wed, 15 Oct 2008 10:31:10 +0000 Received: from lara.cc.fer.hr ([161.53.72.113]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Oct 2008 10:31:10 +0000 Received: from ivoras by lara.cc.fer.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 15 Oct 2008 10:31:10 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: pgsql-performance@postgresql.org From: Ivan Voras Subject: Re: Backup strategies Date: Wed, 15 Oct 2008 12:31:08 +0200 Lines: 52 Message-ID: References: <48F4D693.9000304@lerner.co.il> <48F5BBFC.80404@krogh.cc> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig9463A6BA7821C98E7BDEB3EB" X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: lara.cc.fer.hr User-Agent: Thunderbird 2.0.0.17 (X11/20080925) In-Reply-To: <48F5BBFC.80404@krogh.cc> X-Enigmail-Version: 0.95.0 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200810/81 X-Sequence-Number: 31662 This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig9463A6BA7821C98E7BDEB3EB Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Jesper Krogh wrote: > Ivan Voras wrote: >> Warning: DO NOT do on-the-fly binary backups without snapshots. >> Archiving the database directory with tar on a regular file system, >> while the server is running, will result in an archive that most likel= y >> won't work when restored. >=20 > Even if you do a "pg_start_backup/pg_stop_backup" as specified here: >=20 > http://www.postgresql.org/docs/8.3/interactive/continuous-archiving.htm= l > =3D> Making a Base backup. >=20 > ?? >=20 > It worked when I tested it, but I may just have been darn lucky. No, it should be ok - I just didn't catch up with the times :) At least that's my interpretation of this paragraph in documentation: """Some backup tools that you might wish to use emit warnings or errors if the files they are trying to copy change while the copy proceeds. This situation is normal, and not an error, when taking a base backup of an active database; so you need to ensure that you can distinguish complaints of this sort from real errors...""" It looks like PostgreSQL freezes the state of the "data" directory in this case (and new data goes only to the transaction log - pg_xlog), which effectively creates an application-level snapshot. Good to know. --------------enig9463A6BA7821C98E7BDEB3EB Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI9cZsldnAQVacBcgRAm/SAKCvbae6YHKTxD4z0MtRxjDZld7vPACgr8cG YbPQFsIQlZV9U52gQI1of+k= =ipDp -----END PGP SIGNATURE----- --------------enig9463A6BA7821C98E7BDEB3EB--