Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
От
Kuntal Ghosh
Тема
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits
Дата
Msg-id
CAGz5QCJyq0aVYwTwyDyVC2tdN=7_8e-O4iwnQqa-DhegB3ia5Q@mail.gmail.com
Ответ на
Список
Дерево обсуждения
COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Pavan Deolasee <pavan.deolasee@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Masahiko Sawada <sawada.mshk@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Pavan Deolasee <pavan.deolasee@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Masahiko Sawada <sawada.mshk@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Pavan Deolasee <pavan.deolasee@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Masahiko Sawada <sawada.mshk@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Pavan Deolasee <pavan.deolasee@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Darafei Praliaskouski <me@komzpa.net>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Masahiko Sawada <sawada.mshk@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Pavan Deolasee <pavan.deolasee@gmail.com>
Re: Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits David Steele <david@pgmasters.net>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Simon Riggs <simon@2ndquadrant.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Jeff Janes <jeff.janes@gmail.com>
Re: COPY FREEZE and setting PD_ALL_VISIBLE/visibility map bits Pavan Deolasee <pavan.deolasee@gmail.com>
On Tue, Feb 26, 2019 at 6:46 PM Simon Riggs wrote: > > On Thu, 21 Feb 2019 at 15:38, Kuntal Ghosh wrote: > >> >> Thank you for the patch. It seems to me that while performing COPY >> FREEZE, if we've copied tuples in a previously emptied page > > > There won't be any previously emptied pages because of the pre-conditions required for FREEZE. > Right, I missed that part. Thanks for pointing that out. But, this optimization is still possible for copying frozen tuples in a newly created page, right? If current backend allocates a new page, copies a bunch of frozen tuples in that page, it can set the PD_ALL_VISIBLE in the same operation. -- Thanks & Regards, Kuntal Ghosh EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления