Re: pg_dump: Remove "blob" terminology - Mailing list pgsql-hackers

From Tom Lane
Subject Re: pg_dump: Remove "blob" terminology
Date
Msg-id 1999945.1670002835@sss.pgh.pa.us
Whole thread Raw
In response to Re: pg_dump: Remove "blob" terminology  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: pg_dump: Remove "blob" terminology  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
> On 2022-12-02 Fr 09:18, Tom Lane wrote:
>> The scheme I've vaguely thought about, but not got round to writing,
>> is to merge all blobs with the same owner and ACL into one TOC entry.
>> One would hope that would get it down to a reasonable number of
>> TOC entries in practical applications.  (Perhaps there'd need to be
>> a switch to make this optional.)

> +1 for fixing this. Your scheme seems reasonable. This has been a pain
> point for a long time. I'm not sure what we'd gain by making the fix
> optional.

Well, what this would lose is the ability to selectively restore
individual large objects using "pg_restore -L".  I'm not sure who
out there might be depending on that, but if we assume that's the
empty set I fear we'll find out it's not.  So a workaround switch
seemed possibly worth the trouble.  I don't have a position yet
on which way ought to be the default.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Bogus rte->relkind for EXCLUDED pseudo-relation
Next
From: Andres Freund
Date:
Subject: Re: [RFC] building postgres with meson - v13