Re: Reviewing freeze map code
| От | Andres Freund |
|---|---|
| Тема | Re: Reviewing freeze map code |
| Дата | |
| Msg-id | 20160629170050.zpvcmaz3ni2y75d7@alap3.anarazel.de обсуждение исходный текст |
| Ответ на | Re: Reviewing freeze map code (Amit Kapila <amit.kapila16@gmail.com>) |
| Ответы |
Re: Reviewing freeze map code
|
| Список | pgsql-hackers |
On 2016-06-29 19:04:31 +0530, Amit Kapila wrote: > There is nothing in this record which recorded the information about > visibility clear flag. I think we can actually defer the clearing to the lock release? A tuple being locked doesn't require the vm being cleared. > I think in this approach, it is important to measure the performance > of update, may be you can use simple-update option of pgbench for > various workloads. Try it with different fill factors (-F fillfactor > option in pgbench). Probably not sufficient, also needs toast activity, to show the really bad case of many lock releases.
В списке pgsql-hackers по дате отправления: