Re: where should I stick that backup?

From: Greg Stark <stark(at)mit(dot)edu>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, Bruce Momjian <bruce(at)momjian(dot)us>, Magnus Hagander <magnus(at)hagander(dot)net>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: where should I stick that backup?
Date: 2020-04-18 22:37:09
Message-ID: CAM-w4HPWVOAKQq=Sn79d4jeCb4O-imy--bXFXXL4sF4YEYbh8Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Fwiw, it was common trick in the Oracle world to create a named pipe
to gzip and then write your backup to it. I really like that way of
doing things but I suppose it's probably too old-fashioned to expect
to survive. And in practice while it worked for a manual process for a
sysadmin it's pretty awkward to automate reliably.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-04-19 00:12:42 Re: relocating the server's backup manifest code
Previous Message Justin Pryzby 2020-04-18 20:41:05 Re: WAL usage calculation patch