Re: Updated backup APIs for non-exclusive backups

From: Craig Ringer <craig(at)2ndquadrant(dot)com>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Marco Nenciarini <marco(dot)nenciarini(at)2ndquadrant(dot)it>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Updated backup APIs for non-exclusive backups
Date: 2016-04-25 12:31:16
Message-ID: CAMsr+YHD3mNgPUA+0LZpkRSWw1osE0L+EMwbpr2oPGp-i8kUWQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 24 April 2016 at 23:49, Stephen Frost <sfrost(at)snowman(dot)net> wrote:

>
> Fixing that means using something more complicated than the old method
> and that's a bit of a pain in psql, but that doesn't mean we should tell
> people that the old method is an acceptable approach.
>

+1

Frankly, I don't find doing backups with psql this way interesting. I'm a
bit astonished that anyone's doing it, really. Most of the time I'm doing
anything more complicated than pg_basebackup I've got more flexible tools
at hand than psql too.

\gset should be a workaround for anyone who really wants to do this in psql
for some reason.

--
Craig Ringer http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2016-04-25 12:34:06 Re: Proposed change to make cancellations safe
Previous Message Geoff Winkless 2016-04-25 12:18:20 Re: Rename max_parallel_degree?