Re: pgsql: tableam: Add tuple_{insert, delete, update, lock} and use.

2019-03-24 Thread Andres Freund
Hi, On March 24, 2019 11:17:15 AM PDT, Alexander Korotkov wrote: >Great work, thank you very much! > >On Sun, Mar 24, 2019 at 6:02 AM Andres Freund >wrote: >> Previously both delete/update/lock call-sites and the EPQ mechanism >had >> to have awareness of the specific tuple format to be able

Re: pgsql: tableam: Add tuple_{insert, delete, update, lock} and use.

2019-03-24 Thread Alexander Korotkov
Great work, thank you very much! On Sun, Mar 24, 2019 at 6:02 AM Andres Freund wrote: > Previously both delete/update/lock call-sites and the EPQ mechanism had > to have awareness of the specific tuple format to be able to fetch the > latest version of a tuple. Obviously that needs to be

pgsql: tableam: Add tuple_{insert, delete, update, lock} and use.

2019-03-23 Thread Andres Freund
tableam: Add tuple_{insert, delete, update, lock} and use. This adds new, required, table AM callbacks for insert/delete/update and lock_tuple. To be able to reasonably use those, the EvalPlanQual mechanism had to be adapted, moving more logic into the AM. Previously both delete/update/lock