On Wed, Mar 7, 2018 at 8:30 PM, Alvaro Herrera <alvhe...@2ndquadrant.com> wrote:
> I suggest to create a new function GinPredicateLockPage() that checks > whether fast update is enabled for the index. The current arrangement > looks too repetitive and it seems easy to make a mistake. > BTW, should we also skip CheckForSerializableConflictIn() when fast update is enabled? AFAICS, now it doesn't cause any errors or false positives, but makes useless load. Is it correct? ------ Alexander Korotkov Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
