Re: pg_dump: Remove "blob" terminology
От | Andrew Dunstan |
---|---|
Тема | Re: pg_dump: Remove "blob" terminology |
Дата | |
Msg-id | 34c6f0df-7dc9-9a8c-42e5-c35b55d51711@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 09:18, Tom Lane wrote: > we really need to do something about situations with $BIGNUM > large objects. Currently those tend to run pg_dump or pg_restore > out of memory because of TOC bloat, and we've seen multiple field > reports of that actually happening. > > 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. cheers andrew -- Andrew Dunstan EDB: https://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: