public inbox for [email protected]
help / color / mirror / Atom feedFrom: Wasim Devale <[email protected]>
To: Tom Lane <[email protected]>
Cc: Holger Jakobs <[email protected]>
Cc: [email protected]
Subject: Re: pg_dump
Date: Tue, 13 Aug 2024 12:12:41 +0530
Message-ID: <CAB5fag71Y5bUiO1X+FGUH6o23Qa0PZOQBLVQW3g3bUvPtxkO4Q@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAB5fag579JWutV2KyDcKVPpiba=H55k1vx8sxc8RPKyp8ssgEQ@mail.gmail.com>
<[email protected]>
<CAB5fag6zyWM8BwXDskOCu5OOruxaV9wUjEp-tpTO63EjGXRivQ@mail.gmail.com>
<[email protected]>
Then what might be the solution for it if I am only concerned about using
pg_dump
On Tue, 13 Aug, 2024, 12:03 pm Tom Lane, <[email protected]> wrote:
> Wasim Devale <[email protected]> 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=pg_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
>
view thread (17+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: pg_dump
In-Reply-To: <CAB5fag71Y5bUiO1X+FGUH6o23Qa0PZOQBLVQW3g3bUvPtxkO4Q@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox