Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Subject: Re: Another pg_dump using split and gzip for large  databases
From: Daniel Gustafsson <daniel@yesql.se>
In-Reply-To: <20210729152925.GJ9600@momjian.us>
Date: Thu, 29 Jul 2021 19:15:21 +0200
Cc: jim@jdoherty.net,
 pgsql-docs@lists.postgresql.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <04E6A89E-19FC-4181-9D95-96B71482944F@yesql.se>
References: <162653459215.701.6323855956817776386@wrigleys.postgresql.org>
 <20210728234605.GA9600@momjian.us>
 <A38B4103-419D-46F7-9CCF-983DC826723D@yesql.se>
 <20210729145855.GF9600@momjian.us>
 <247A4697-C00B-47A9-851A-D213CA83A378@yesql.se>
 <20210729152925.GJ9600@momjian.us>
To: Bruce Momjian <bruce@momjian.us>
Archived-At: 
 <https://www.postgresql.org/message-id/04E6A89E-19FC-4181-9D95-96B71482944F%40yesql.se>
Precedence: bulk

> On 29 Jul 2021, at 17:29, Bruce Momjian <bruce@momjian.us> wrote:
>=20
> On Thu, Jul 29, 2021 at 05:23:20PM +0200, Daniel Gustafsson wrote:
>>> On 29 Jul 2021, at 16:58, Bruce Momjian <bruce@momjian.us> wrote:
>>=20
>>> OK, I can adjust it to say "GNU split" or just skip this addition.
>>=20
>> I don't have strong feelings either way, with a slight preference for =
writing
>> it as "GNU split" since it's still a good tip for a large amount of =
readers.
>=20
> Yes, I am on the fence for the same reasons but lean toward moving
> forward for your same reasons.

Making it two separate examples is a good idea, tipping the scale to a =
+1 from me.

+     If using <application>GNU split</application>, it is possible to
A small nitpick is that we write this as GNU =
<application>..</application>
elsewhere on this page (like GNU tar for example).

--
Daniel Gustafsson		https://vmware.com/