Hi,
Working on rebasing the pluggable storage patch on the current version
of this.
On 2018-07-26 17:09:08 +0530, Ashutosh Bapat wrote:
> Done. I also noticed that slot_getattr() optimizes the cases when the
> requested attributes is NULL or is missing from a tuple. Given that a
> custom TupleTableSlot type can have its own optimizations for the
> same, added a new call back getattr() to obtain value of a given
> attribute from slot. The callback is called from slot_getattr().
I'm quite against this. This is just proliferation of callbacks without
much use. Why do you think this is helpful? I think it's much better
to go back to a single callback to deform here.
Greetings,
Andres Freund