Re: pg_dump: Remove "blob" terminology
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew@dunslane.net>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>,
Daniel Gustafsson <daniel@yesql.se>,
PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2022-12-02T17:40:35Z
Lists: 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
Commits
-
pg_dump: Remove move "blob" terminology
- 94851e4b9050 16.0 landed
-
pg_dump: Remove "blob" terminology
- 35ce24c333cf 16.0 landed