From: Tom Lane <tgl@sss.pgh.pa.us>
To: Scott Marlowe <smarlowe@g2switchworks.com>
Cc: Pallav Kalva <pkalva@deg.cc>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgres 8.0 Backups
Date: Mon, 24 Jan 2005 13:05:00 -0500
Message-ID: <23143.1106589900@sss.pgh.pa.us> (raw)
In-Reply-To: <1106586565.16640.90.camel@state.g2switchworks.com>
References: <41F52694.1090309@deg.cc>
<1106586565.16640.90.camel@state.g2switchworks.com>
Scott Marlowe <smarlowe@g2switchworks.com> writes:
> On Mon, 2005-01-24 at 10:47, Pallav Kalva wrote:
>> I am working on a backup script for Postgres 8.0 online backups and
>> since i have to copy the whole pgdata directory , i am wondering after i
>> copy the pgdata directory can I run gzip or tar on the data directory ?
> Generally speaking, file system level backups are not the best way to
> backup postgresql, since they require either shutting down the server or
> using a snapshot file system to get a coherent backup.
In the context of online backup operations, that advice isn't relevant
anymore ...
Personally I would do "tar cfz pgdata.tar.gz $PGDATA" or equivalent,
rather than making an explicit copy of the directory tree first.
regards, tom lane
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, smarlowe@g2switchworks.com, pkalva@deg.cc
Subject: Re: Postgres 8.0 Backups
In-Reply-To: <23143.1106589900@sss.pgh.pa.us>
References: <41F52694.1090309@deg.cc> <1106586565.16640.90.camel@state.g2switchworks.com> <23143.1106589900@sss.pgh.pa.us>
* 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