Path: csiph.com!feeder.erje.net!1.eu.feeder.erje.net!news.albasani.net!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Rainer Weikusat <rweikusat@talktalk.net>
Newsgroups: comp.databases.postgresql
Subject: Re: Issues with backing up Postgres by copying folder
Date: Fri, 28 Apr 2017 12:39:18 +0100
Lines: 33
Message-ID: <8737csyd5l.fsf@doppelsaurus.mobileactivedefense.com>
References: <smBIA.407$xR7.221@fx28.iad> <87h91evna3.fsf@doppelsaurus.mobileactivedefense.com> <%KzMA.146910$3c5.37564@fx34.iad>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: individual.net sCjSqM7D0tzpLniX3YNQrQhbObuEoD81MpcfAOdVabJumG4Sc=
Cancel-Lock: sha1:qxLi4p/w6vQOrM2H85Hn4MORVL8= sha1:4VqBaU+r6XYKSQYRlXrBiTTvqVg=
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.4 (gnu/linux)
Xref: csiph.com comp.databases.postgresql:747

DFS <nospam@dfs.com> writes:
> On 4/23/2017 5:15 PM, Rainer Weikusat wrote:
>> DFS <nospam@dfs.com> writes:
>>> Windows
>>> Postgres 9.6.2
>>>
>>> On install I set the /data directory to a data drive (D:\)
>>>
>>> How much trouble will it cause if I:
>>>
>>> 1) backup that entire /data directory by copying it to a backup place
>>> 2) reinstall Postgres (and set the /data directory to the same
>>>     location as before)
>>> 3) copy over the new /data directory with my backup?
>>>
>>> No pgdump - just copy and replace files.
>>
>> Is there a reason why you want to follow such a cumbersome and fragile
>> procedure?
>
>
> 1) it seems very uncumbersome to just copy a folder to a backup drive

Why do you want to hunt the system for "folders" based on some
assumption about the disk usage of the DBMS instead of just using
pg_dump?

> 2) why is it 'fragile'?

Have you verified that your assumptions about the disk usage are correct
by checking the source and received from assurance from the developers
that they're set in stone?