Re: Reviewing freeze map code
От | Jim Nasby |
---|---|
Тема | Re: Reviewing freeze map code |
Дата | |
Msg-id | c954f72f-6900-346e-d2fc-e9a7a3d0efcf@BlueTreble.com обсуждение исходный текст |
Ответ на | Re: Reviewing freeze map code (Andres Freund <andres@anarazel.de>) |
Ответы |
Re: Reviewing freeze map code
|
Список | pgsql-hackers |
On 7/1/16 2:23 PM, Andres Freund wrote: >> > The only >> > cost of that is that vacuum will come along and mark the page >> > all-visible again instead of skipping it, but that's probably not an >> > enormous expense in most cases. > I think the main cost is not having the page marked as all-visible for > index-only purposes. If it's an insert mostly table, it can be a long > while till vacuum comes around. ISTM that's something that should be addressed anyway (and separately), no? -- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com 855-TREBLE2 (855-873-2532) mobile: 512-569-9461
В списке pgsql-hackers по дате отправления: