Re: Performance Improvement by reducing WAL for Update Operation
От | Amit kapila |
---|---|
Тема | Re: Performance Improvement by reducing WAL for Update Operation |
Дата | |
Msg-id | 6C0B27F7206C9E4CA54AE035729E9C383BEAFFE7@szxeml509-mbs обсуждение исходный текст |
Ответ на | Re: Performance Improvement by reducing WAL for Update Operation (Simon Riggs <simon@2ndQuadrant.com>) |
Ответы |
Re: Performance Improvement by reducing WAL for Update Operation
|
Список | pgsql-hackers |
On Friday, January 11, 2013 11:09 PM Simon Riggs wrote: On 11 January 2013 17:08, Amit kapila <amit.kapila@huawei.com> wrote: >>> Just reviewing the patch now, making more sense with comments added. > >>>In heap_delta_encode() do we store which columns have changed? > >> Not the attribute bumberwise, but offsetwise it is stored. > (Does that mean "numberwise"??) Yes. > Can we identify which columns have changed? i.e. 1st, 3rd and 12th columns? As per current algorithm, we can't as it isbased on offsets. What I mean to say is that the basic idea to reconstruct tuple during recovery is copy data from oldtuple offset-wise (offsets stored in encoded tuple) and use new data (modified column data) from encoded tuple directly.So we don't need exact column numbers. With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: