Re: Performance Improvement by reducing WAL for Update Operation

On 11 January 2013 18:11, Amit kapila <amit(dot)kapila(at)huawei(dot)com> wrote:

>> Can we identify which columns have changed? i.e. 1st, 3rd and 12th columns?
> As per current algorithm, we can't as it is based on offsets.
> What I mean to say is that the basic idea to reconstruct tuple during recovery
> is copy data from old tuple 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.

Another patch is going through next CF related to reassembling changes
from WAL records.

To do that efficiently, we would want to store a bitmap showing which
columns had changed in each update. Would that be an easy addition, or
is that blocked by some aspect of the current design?

The idea would be that we could re-construct an UPDATE statement that
would perform exactly the same change, yet without needing to refer to
a base tuple.

--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services