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 1sdlFG-000hEL-4n for pgsql-admin@arkaria.postgresql.org; Tue, 13 Aug 2024 06:43:02 +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 1sdlFD-0028X0-Aw for pgsql-admin@arkaria.postgresql.org; Tue, 13 Aug 2024 06:42:59 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1sdlFC-0028Ws-Ru for pgsql-admin@lists.postgresql.org; Tue, 13 Aug 2024 06:42:58 +0000 Received: from mail-ej1-x62c.google.com ([2a00:1450:4864:20::62c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1sdlFA-004Uuh-4q for pgsql-admin@lists.postgresql.org; Tue, 13 Aug 2024 06:42:57 +0000 Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a7d2a9a23d9so561583266b.3 for ; Mon, 12 Aug 2024 23:42:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1723531375; x=1724136175; 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=wpMmWVQJHr/fukFO8aaudPAxLpAj28MRdtDeLp2Ex4E=; b=d3sv/TweF344RthVZg453m18dNpHRmkGgRq6d0+dmvQYu0EKkidIUkPCwZQx6Tnujk ceJqYsaiUXziNljYpDrOvUKnvNs8r6NeHNz2p+emkNBG78vIqXOrJ8XHEZXPpQFZGjix UU4mSbz/DpxcGnrGbg+ajS6FiaO14uk6nge8g99K+6X6M/hE/rLe6PmBVFZ73LszoIhb ghi8k+Y6t7E41k4SYTC0qwBkvlFLXyVsbDZM5kEckc8qSPXxZklUxnlMXj9DtvFcpWZK yhQxHeXhx+0mitxPaeq3P8svEJ2so8BkrrqsXhNSS14X72Lzw9SUGaSklgePgPXFp1H5 g6dw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1723531375; x=1724136175; 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=wpMmWVQJHr/fukFO8aaudPAxLpAj28MRdtDeLp2Ex4E=; b=obaBKShq5AuxHjccWVpCxzhw7S1qyOPGQ+S8H56ap30NwelwECWZ+sjPey4dIa3NE5 f+Y32EF5KsF4crEaSMSrEmDPK2IMWh6mc7JcaHuSIsVYLcCX8AHeO/hDg0oVr9MtY0qv jptqKBgvTFwLAuzgUJaBG5TA7d5OLUN9m2xnL0WIVNgsrQtw40KESrqdjJkIXIAEeW1e LexcrgAQYmgPTgQqoEDehUQ9g1U3fU55a1nD5hF6GtbJ//A9fwBDnKZw7mKY5a95O8W6 4W8kLbpv7SUqKNIz6V3xXGUdsuLEOCy8qW0Vcef3ADe0I4MTHIa4m7rHVtMNYGrPq9dI eHvg== X-Forwarded-Encrypted: i=1; AJvYcCX2JyolqW3I5t1W2QPh3yDekMAmAZaFme1RWPiHuwz8jKyGdZo2QYpKr7eFIr8UtZ2UnMGT+XKvuT3IBc1HXbHbt0+qGFfo0JqmH7nvfpqVNA== X-Gm-Message-State: AOJu0YzwUVOL9KZBRnghkfHhcDf/i+Fc8uFTzmN5ShUVwGw/Jp/PlaqK auTIK/H/GbmUhec5XMHJ1yZIIGDUNJ0I6wlrgHesH19wB8SjjeYFHwPpo0C4zryFEyJ/A2qZo2g 07haBTYZlomginuS6RMDV5hoisEE= X-Google-Smtp-Source: AGHT+IF9TyLOFwFhtFV8dGhfUzhdppFpkbU5J1XiDfo9LnKrvaTwMXbIS7eeHhqqBUShduUHEHV+W59ZEw/6T6yFBi8= X-Received: by 2002:a17:907:f796:b0:a77:e55a:9e91 with SMTP id a640c23a62f3a-a80ed204a6cmr186037466b.19.1723531373891; Mon, 12 Aug 2024 23:42:53 -0700 (PDT) MIME-Version: 1.0 References: <7b149653-4992-9285-d9af-53929497f4e8@jakobs.com> <1170092.1723530800@sss.pgh.pa.us> In-Reply-To: <1170092.1723530800@sss.pgh.pa.us> From: Wasim Devale Date: Tue, 13 Aug 2024 12:12:41 +0530 Message-ID: Subject: Re: pg_dump To: Tom Lane Cc: Holger Jakobs , pgsql-admin@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000004cd48c061f8aebe9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000004cd48c061f8aebe9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable 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, wrote: > 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 > --0000000000004cd48c061f8aebe9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

Then what might be the solution for it if I am only concerne= d 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
--0000000000004cd48c061f8aebe9--