Re: pg_dump

From: Wasim Devale <wasimd60(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Holger Jakobs <holger(at)jakobs(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: pg_dump
Date: 2024-08-13 06:42:41
Message-ID: CAB5fag71Y5bUiO1X+FGUH6o23Qa0PZOQBLVQW3g3bUvPtxkO4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

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, <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Wasim Devale <wasimd60(at)gmail(dot)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=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
>

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message William Sescu (Suva) 2024-08-13 08:07:04 No Message "PostgreSQL, contrib, and documentation successfully made. Ready to install."
Previous Message Tom Lane 2024-08-13 06:33:20 Re: pg_dump