On Tue, Mar 21, 2017 at 11:54:25PM +0530, Pavan Deolasee wrote: > We can also save HEAP_WARM_UPDATED flag since this is required only for > abort-handling case. We can find a way to push that information down to the > old > tuple if UPDATE aborts and we detect the broken chain. Again, not fully > thought > through, but doable. Of course, we will have to carefully evaluate all code > paths and make sure that we don't lose that information ever. > > If the consumption of bits become a deal breaker then I would first trade the > HEAP_LATEST_TUPLE bit and then HEAP_WARM_UPDATED just from correctness > perspective.
I don't think it makes sense to try and save bits and add complexity when we have no idea if we will ever use them, but again, I am back to my original question of whether we have done sufficient research, and if everyone says "yes", I am find with that. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
