From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, David Steele <david(at)pgmasters(dot)net>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Remove Deprecated Exclusive Backup Mode |
Date: | 2020-07-01 19:47:13 |
Message-ID: | 20200701194713.GB14470@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jul 1, 2020 at 01:23:21PM -0400, Stephen Frost wrote:
> > Or, how about we require them to provide the backup label contents in its
> > entirety? Which I believe does contain that WAL portion? The downside of
> > that is that it would be multiline which might screw with shellscripts.
>
> This is getting a bit beyond the pale imv if we're talking about trying
> to cater to software that can't manage to handle a multi-line result or
> multi-line argument to a function.
Seems to work for me in bash:
$ X='a
> b
> c'
$ echo "$X"
a
b
c
$ echo $X
a b c
You need the double quotes around the variable name.
--
Bruce Momjian <bruce(at)momjian(dot)us> https://momjian.us
EnterpriseDB https://enterprisedb.com
The usefulness of a cup is in its emptiness, Bruce Lee
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2020-07-01 19:49:44 | Re: Remove Deprecated Exclusive Backup Mode |
Previous Message | Bruce Momjian | 2020-07-01 19:45:08 | Re: max_slot_wal_keep_size and wal_keep_segments |