Re: pg_dump: Remove "blob" terminology
От | Andrew Dunstan |
---|---|
Тема | Re: pg_dump: Remove "blob" terminology |
Дата | |
Msg-id | 9738eb42-9ea6-1a15-6fd3-bf711bfdcb2d@dunslane.net обсуждение исходный текст |
Ответ на | Re: pg_dump: Remove "blob" terminology (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: pg_dump: Remove "blob" terminology
|
Список | pgsql-hackers |
On 2022-12-02 Fr 12:40, Tom Lane wrote: > 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. > > OK, fair point. I suspect making the batched mode the default would gain more friends than enemies. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: