Re: crash-safe visibility map, take three
От | Robert Haas |
---|---|
Тема | Re: crash-safe visibility map, take three |
Дата | |
Msg-id | AANLkTi=K=26Nkx48H9nmUcmJNcuWhL60VqCy8OXCRr28@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: crash-safe visibility map, take three (Jesper Krogh <jesper@krogh.cc>) |
Ответы |
Re: crash-safe visibility map, take three
Re: crash-safe visibility map, take three |
Список | pgsql-hackers |
On Wed, Jan 5, 2011 at 3:22 PM, Jesper Krogh <jesper@krogh.cc> wrote: > Given a crash-safe visibility map, what purpuse does the PD_ALL_VISIBLE bit > serve? If we modify a page on which PD_ALL_VISIBLE isn't set, we don't attempt to update the visibility map. In theory, this is an important optimization to reduce contention on the visibility map page, since there are something like 64K heap pages per visibility map page. In practice, I'm not sure in what workloads it matters or by how much. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: