From: Kevin Grittner <Kevin.Grittner@wicourts.gov>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
To: pgsql-admin@postgresql.org
Subject: Re: Hard link backup strategy
Date: Tue, 31 Mar 2009 09:11:55 -0500
Message-ID: <49D1DE5B.EE98.0025.0@wicourts.gov> (raw)
In-Reply-To: <200903311400.26346@zmi.at>
References: <49CB9D8302000025000257DF@gwmta.wicourts.gov>
<200903270843.45051@zmi.at>
<49D0B91B.EE98.0025.0@wicourts.gov>
<200903311400.26346@zmi.at>
Michael Monnerie <michael.monnerie@is.it-management.at> wrote:
> It is no problem if B reads, A can copy without a problem, even
> without the cp before mv.
B could open the file while it is being copied, and read to the
current end of file before A has finished copying. If we used rsync
it would, by default, copy to a temporary file name in the target
directory and mv to the right name when complete, but we prefer the cp
to a temp directory and explicitly mv, because of the subsequent rsync
steps copyig out of the target directory.
-Kevin
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 using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: Kevin.Grittner@wicourts.gov, michael.monnerie@is.it-management.at
Subject: Re: Hard link backup strategy
In-Reply-To: <49D1DE5B.EE98.0025.0@wicourts.gov>
* 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