Re: [GENERAL] Using cp to back up a database? - Mailing list pgsql-general

From Ron Johnson
Subject Re: [GENERAL] Using cp to back up a database?
Date
Msg-id 1f73e7e9-e41b-2e7e-d705-f0f6b71de52d@cox.net
Whole thread Raw
In response to [GENERAL] Using cp to back up a database?  (Ron Johnson <ron.l.johnson@cox.net>)
Responses Re: [GENERAL] Using cp to back up a database?  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-general

Sure I want a consistent database.  Why doesn't?

But log shipping requires you to rsync/var/lib/pgsql/data  to the remote server, and that's consistent, so why wouldn't rsync to a local directory also be consistent?

On 10/09/2017 08:51 AM, Larry Rosenman wrote:

If you want a consistent database (you *REALLY* do), pg_dump is the correct tool.

 

-- 

Larry Rosenman                     http://www.lerctr.org/~ler

Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org

US Mail: 5708 Sabbia Drive, Round Rock, TX 78665-2106

 

 

From: <pgsql-general-owner@postgresql.org> on behalf of Ron Johnson <ron.l.johnson@cox.net>
Date: Monday, October 9, 2017 at 8:41 AM
To: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
Subject: [GENERAL] Using cp to back up a database?

 

Hi,

v8.4.20

This is what the current backup script uses:

/usr/bin/psql -U postgres -c "SELECT pg_start_backup('Incrementalbackup',true);"

cp -r /var/lib/pgsql/data/* $dumpdir/data/

/usr/bin/psql -U postgres template1 -c "SELECT pg_stop_backup();"



Should it use rsync or pg_dump instead?

Thanks



-- 
World Peace Through Nuclear Pacification

pgsql-general by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [GENERAL] Using cp to back up a database?
Next
From: Achilleas Mantzios
Date:
Subject: Re: [GENERAL] Using cp to back up a database?