From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Using cp to back up a database? |
Date: | 2017-10-09 16:41:37 |
Message-ID: | 835f7baa-8517-eb4e-b9ee-27170adea759@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/09/2017 11:33 AM, Jeff Janes wrote:
> On Mon, Oct 9, 2017 at 6:40 AM, Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net
> <mailto:ron(dot)l(dot)johnson(at)cox(dot)net>> wrote:
>
> 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();"
>
>
> That's fine, as long as you have a wal archive. Although I don't know what
> is "Incremental" about it.
From reading the docs, that field is just a label with no intrinsic meaning.
--
World Peace Through Nuclear Pacification
From | Date | Subject | |
---|---|---|---|
Next Message | Igal @ Lucee.org | 2017-10-09 16:44:41 | Permissions for Web App |
Previous Message | mj0nes | 2017-10-09 16:33:29 | pg_start/stop_backup naming conventions |