Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEa8B-002Ihz-4z for pgsql-general@arkaria.postgresql.org; Tue, 04 Jun 2024 19:47:40 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1sEa8A-002ExB-0M for pgsql-general@arkaria.postgresql.org; Tue, 04 Jun 2024 19:47:38 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sEa89-002Ex2-K9 for pgsql-general@lists.postgresql.org; Tue, 04 Jun 2024 19:47:37 +0000 Received: from mail-yb1-xb33.google.com ([2607:f8b0:4864:20::b33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sEa87-0000Rs-10 for pgsql-general@lists.postgresql.org; Tue, 04 Jun 2024 19:47:37 +0000 Received: by mail-yb1-xb33.google.com with SMTP id 3f1490d57ef6-dfa71ded97bso163672276.1 for ; Tue, 04 Jun 2024 12:47:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aweber.com; s=2018090500; t=1717530453; x=1718135253; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=qS6Gx/vyRniXaAF/ydLPwzAswr5Do/0QE8CN7WE8oJM=; b=O8rf54yb0n87ofTdxed64oMZtvfWjSkGfeYvRv0Djj/vckF7C2sN7WcxccclNGp4lH kAxkHOL5zoyrCwkC24yBWMTWa5ENme4hNP+44vcJ0clW0CivUt5f1KUM6wUfBjPcLeof fB7T1WvdShCw7gAuaUT9GcHVzJZvkSIpC5arz7yEZ3hS1MkRv+w6Egf2XyCznN/YwLWe K55oY2RWGQf0FKe+Frcx/N4DA3Q3hELyeYw03NdjSvgncQfMsoJeCj0I7jesDB1VTUxR NZZ8TZ4oo1qyQcvVk3RCA+Y32M7G0Bq8y4desDj7TIGf1WzQ+rEfscsUUhi02QbsBi5p 07Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1717530453; x=1718135253; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=qS6Gx/vyRniXaAF/ydLPwzAswr5Do/0QE8CN7WE8oJM=; b=BD1Dtdad37P+b4oC7WhFmT1AtN3wVUBXdzpyooft9hdd8J90sYTPowSlehPixU4rSM At2xPcLJ/NBmvKCdrrDaoJObpGGFyUVIJ/t8qdrpPBC2syl0O2x0LEFYJQY5s+cpSUM6 E708TbM28oJgFd8nk3X6hhISWUaSx1snYmlilL5w3AiIJbvvhK9wcGqqIFs0aZ8HrR2y VRgp4d9Qn5JYFuYsjujzfZSMYnsvR1F9Xl46BPcj/EoJLH179lSdqGhAwyU+noj8jTf5 pEIALlaChBFCWZp4B4UwQksDvnLeBNFsOHfhMSDfTojvu7nRn5DgNakKbcunD2exDsdn y0OQ== X-Gm-Message-State: AOJu0YwNB12ME1zrMK5YUCp1oXanRoCHsKPLSR960UAoOJrec9VJLuW8 FEGUBdFMbAnSvxGH8WN0/S2RrITVJcbLpqn8vO2YcKcr2un9ztY99yYX4SmtzNAJoq6zpvP/dxs TDNgc8I+hB9Na6e95Z+t6dmHwsxIPLhsxaATcAM8Jaew3CCb3yEIX1uix X-Google-Smtp-Source: AGHT+IEan3SQufkmluuKjhXf0VT4kgpv6TCnkAP1lQ3BGZXiQJ44+E/4cIebZUhmxeAaM43JXhwRdui/1jyFn+M3SrA= X-Received: by 2002:a25:b78c:0:b0:df4:e4fc:16a0 with SMTP id 3f1490d57ef6-dfab854d183mr3017560276.13.1717530453506; Tue, 04 Jun 2024 12:47:33 -0700 (PDT) MIME-Version: 1.0 References: <25e9749c-ff38-4832-9b26-386cac33b3d8@aklaver.com> <7005ac8c-2f83-4122-9172-04bca268f987@aklaver.com> <4b28e899-d802-43ce-b20b-655a9077f08f@gmail.com> In-Reply-To: From: Gavin Roy Date: Tue, 4 Jun 2024 15:47:22 -0400 Message-ID: Subject: Re: Purpose of pg_dump tar archive format? To: Ron Johnson Cc: "pgsql-generallists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000929424061a15b8fd" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000929424061a15b8fd Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Tue, Jun 4, 2024 at 3:15=E2=80=AFPM Ron Johnson wrote: > > But why tar instead of custom? That was part of my original question. > I've found it pretty useful for programmatically accessing data in a dump for large databases outside of the normal pg_dump/pg_restore workflow. You don't have to seek through one large binary file to get to the data section to get at the data. --000000000000929424061a15b8fd Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Tue, Jun 4, 2024 at 3:15=E2=80=AFPM Ro= n Johnson <ronljohnsonjr@gmai= l.com> wrote:

But why tar instead of custom? That was part of my original question.=

I've found it prett= y useful for programmatically accessing data in a dump for large databases = outside of the normal pg_dump/pg_restore workflow. You don't have to se= ek through one large binary file to get to the data section to get at the d= ata.
--000000000000929424061a15b8fd--