Re: pg_dump

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_dump
Date: 2024-08-13 12:04:37
Message-ID: CANzqJaD7E6WR_fytkTcjHnU9nX4ktHR7WswbRUDZQdiPB+9Sqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

"Free your mind, and *pg_dump* will follow." Maybe *En Vogue*, but
probably not.

On Tue, Aug 13, 2024 at 2:43 AM Wasim Devale <wasimd60(at)gmail(dot)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 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
>>
>

--
Death to America, and butter sauce.
Iraq lobster!

In response to

Browse pgsql-admin by date

  From Date Subject
Next Message Ron Johnson 2024-08-13 12:05:33 Re: pg_dump
Previous Message Domen Šetar 2024-08-13 09:56:53 Function problem