Re: TupleTableSlot abstraction

From: Andres Freund <andres(at)anarazel(dot)de>
To: pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Amit Khandekar <amitdkhan(dot)pg(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Subject: Re: TupleTableSlot abstraction
Date: 2018-11-17 00:46:42
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers


On 2018-11-13 15:30:21 -0800, Andres Freund wrote:
> What I'm now planning to do is to go through the big comment in
> tuptable.h and update that to the new world. While I'm not convinced
> that that that's the best place for it, it needs to be accurate.
> Furthermore:
> - More comment polishing
> - I'll probably split the commits up a bit further (particulary JIT
> ignoring virtual tuple slots, inlining the hot path of
> slot_getsomeattrs())
> - serious commit message polishing

I've done all of that now, and pushed it. Thanks Ashutosh, Amit
Khandekar and everyone else.

On to pluggable storage...



In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Justin Pryzby 2018-11-17 01:23:44 Re: pg11.1 jit segv
Previous Message Andres Freund 2018-11-17 00:45:25 Re: Why do pg_upgrade's test use the serial schedule? (actual thread)