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 1sdqGk-001Tt1-9A for pgsql-admin@arkaria.postgresql.org; Tue, 13 Aug 2024 12:04:54 +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 1sdqGj-003Udz-0S for pgsql-admin@arkaria.postgresql.org; Tue, 13 Aug 2024 12:04:53 +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 1sdqGi-003Udq-LW for pgsql-admin@lists.postgresql.org; Tue, 13 Aug 2024 12:04:52 +0000 Received: from mail-oo1-xc33.google.com ([2607:f8b0:4864:20::c33]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdqGg-004e7z-Gb for pgsql-admin@lists.postgresql.org; Tue, 13 Aug 2024 12:04:51 +0000 Received: by mail-oo1-xc33.google.com with SMTP id 006d021491bc7-5d8060662a1so3125209eaf.2 for ; Tue, 13 Aug 2024 05:04:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723550689; x=1724155489; darn=lists.postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=2d76qENQ+eJl0veQv5W/pQrS1AJHtEbUl686/UHHxYE=; b=XIL/b36gNgcnDL7GyLwhTda+DDCA8zSASXLlYn7JD0ykPCgEx/VKXjcVJsM8iyq4QC NiNvIB4gDWH93cYJDRuWKaWMW0ZpMod8c581BVtby7WffXvoDVpPUZWWOh70PxbL8hcW 6BfzLOwET451v+JFAgmSSaxRA8LfgP7Dq6SKcGyRTDS70/G+QVhSzGy8/GmOmDaufHvP f5vNlu8mI5fAffi3pEGdVANexXrD9nqdDlTtEzndfqMZzDsUN6Ct4sLQhNSeqEpwvFGR Fmv6s3BJMjQf673OECbRqOCQWGR4HTD7EUjQWLQqkqLQcDMPxSETcpcxVayLE7+Uv+Xc Uimg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723550689; x=1724155489; h=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=2d76qENQ+eJl0veQv5W/pQrS1AJHtEbUl686/UHHxYE=; b=hqNdn+ssXKY12xrjB+2Hckfh3eZkSyaVPlD41i/zvEKMiGyq3Vr3lAWMe+knJYPjG1 n+6+dM1bQ+N0UqXXHzKxMhLSgQ2E9iqZQqy9YKfArbt0R5nRC+8KdYfGsHC9LTgxmV6p QqDiRHs/Vh3HblwJ0quy2BVjPgnU+rNtlay6ePH51QYMtIhK2rU+tiucQojbJ3fjIxpu k82eMARXkdt5Lpx6xB4irol5QA5ftYQdKc1Y3VJHBoVUSBiUGCnf2w3hgFvTC11yP7i1 RqJbA6qCQPRyYbZoPhVt+WMaeueHLUExjYfPea7j+MowSDSiip80lriy+gBN0LhK2xQo FlxQ== X-Gm-Message-State: AOJu0Yw/tPQ5tl1hD48aQgScHS3lgKjlhWlD1gAcJb2Nci6MxmqsFcLu jTPJMnaltCe/Iu9EKLjWVx1VtpPemWvVeu8iZUPDHlnIAOYnNQxqjGfQwHnn7abnhyqdjBecPGs PV6Pp1lMbZgoDjv8Q6AJ5eMf5o0A1Gg== X-Google-Smtp-Source: AGHT+IHq8JcyQ0hdIcnQjlBLERduMaplPAGJmFzIhR0b+PWFZl6Pl0qKK71VvBp/VQc/5dED1wO8hEs5QgGCjv4DmME= X-Received: by 2002:a05:6820:1c90:b0:5c4:144b:1ff9 with SMTP id 006d021491bc7-5da689abb9bmr4299142eaf.5.1723550688519; Tue, 13 Aug 2024 05:04:48 -0700 (PDT) MIME-Version: 1.0 References: <7b149653-4992-9285-d9af-53929497f4e8@jakobs.com> <1170092.1723530800@sss.pgh.pa.us> In-Reply-To: From: Ron Johnson Date: Tue, 13 Aug 2024 08:04:37 -0400 Message-ID: Subject: Re: pg_dump To: Pgsql-admin Content-Type: multipart/alternative; boundary="0000000000008ab602061f8f6ac5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008ab602061f8f6ac5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable "Free your mind, and *pg_dump* will follow." Maybe *En Vogue*, but probably not. On Tue, Aug 13, 2024 at 2:43=E2=80=AFAM Wasim Devale w= rote: > Then what might be the solution for it if I am only concerned about using > pg_dump > > On Tue, 13 Aug, 2024, 12:03=E2=80=AFpm Tom Lane, wrot= e: > >> Wasim Devale writes: >> > I did one thing, we can exclude the toast table in the pg_dump command >> that >> > has the BLOBS data for a particular table. >> > --exclude-table-data=3Dpg_toast.pg_toast_10176226 >> >> Utterly pointless. pg_dump does not dump toast tables as such; >> it's only concerned with their parent "regular" tables. It will >> fetch data from the regular tables, and it's not concerned with >> the server-side implementation detail that some of that data >> might be coming out of a toast table. >> >> regards, tom lane >> > --=20 Death to America, and butter sauce. Iraq lobster! --0000000000008ab602061f8f6ac5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
"Free your mind, and pg_dump will follow.= "=C2=A0 Maybe=C2=A0En Vogue, but probably not.

On Tue, Aug 13, 2= 024 at 2:43=E2=80=AFAM Wasim Devale <wasimd60@gmail.com> wrote:

Then what might be the solution for it = if I am only concerned about using pg_dump


On Tue= , 13 Aug, 2024, 12:03=E2=80=AFpm Tom Lane, <tgl@sss.pgh.pa.us> wrote:
Wasim Devale <wasimd60@gmail= .com> writes:
> I did one thing, we can exclude the toast table in the pg_dump command= that
> has the BLOBS data for a particular table.
> --exclude-table-data=3Dpg_toast.pg_toast_10176226

Utterly pointless.=C2=A0 pg_dump does not dump toast tables as such;
it's only concerned with their parent "regular" tables.=C2=A0= It will
fetch data from the regular tables, and it's not concerned with
the server-side implementation detail that some of that data
might be coming out of a toast table.

=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 regards, tom lane


--
Death to America, and butter sauce.
Iraq lobster!
<= /div>
--0000000000008ab602061f8f6ac5--