Re: tableam vs. TOAST
От | Robert Haas |
---|---|
Тема | Re: tableam vs. TOAST |
Дата | |
Msg-id | CA+TgmoYbrSz13Mn+2=6bQvLju-tRXB9FAA4GQpqdZXro80Expw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: tableam vs. TOAST (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: tableam vs. TOAST
Re: tableam vs. TOAST |
Список | pgsql-hackers |
On Fri, Sep 6, 2019 at 10:59 AM Robert Haas <robertmhaas@gmail.com> wrote: > On Thu, Sep 5, 2019 at 4:07 PM Andres Freund <andres@anarazel.de> wrote: > > Yea, makes sense to me. > > OK, done. Here's the remaining patches again, with a slight update to > the renaming patch (now 0002). In the last version, I renamed > toast_insert_or_update to heap_toast_insert_or_update but did not > rename toast_delete to heap_toast_delete. Actually, I'm not seeing > any particular reason not to go ahead and push the renaming patch at > this point also. And, hearing no objections, done. Here's the last patch back, rebased over that renaming. Although I think that Andres (and Tom) are probably right that there's room for improvement here, I currently don't see a way around the issues I wrote about in http://postgr.es/m/CA+Tgmoa0zFcaCpOJCsSpOLLGpzTVfSyvcVB-USS8YoKzMO51Yw@mail.gmail.com -- so not quite sure where to go next. Hopefully Andres or someone else will give me a quick whack with the cluebat if I'm missing something obvious. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Вложения
В списке pgsql-hackers по дате отправления: