Re: Using cp to back up a database?

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Achilleas Mantzios <achill(at)matrix(dot)gatewaynet(dot)com>
Cc: PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Using cp to back up a database?
Date: 2017-10-09 14:13:36
Message-ID: CAB7nPqTMmKAz602ykFDnr7QyRfS8Sj+hsc0W487NbjGyxs6Vfw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 9, 2017 at 11:09 PM, Achilleas Mantzios
<achill(at)matrix(dot)gatewaynet(dot)com> wrote:
> On 09/10/2017 16:51, Larry Rosenman wrote:
>
> If you want a consistent database (you *REALLY* do), pg_dump is the correct
> tool.
>
> In all pg conferences I have been, ppl scream : do not use pg_dump for
> backups :)

It depends on what you are trying to achieve, pg_dump can be fine for
small-ish databases. By relying on both logical (pg_dump) and physical
backups (base backups) brings more insurance in face of a disaster.
--
Michael

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ron Johnson 2017-10-09 14:15:15 Re: Using cp to back up a database?
Previous Message Achilleas Mantzios 2017-10-09 14:09:39 Re: Using cp to back up a database?