Re: asynchronous and vectorized execution

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: asynchronous and vectorized execution
Date: 2016-05-09 18:33:37
Message-ID: CANP8+jLdTLog_C_0VEmxMQab=GCmcK4=CwYE6wgTLAa96FFzpw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9 May 2016 at 19:33, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:

> I believe there are other people thinking about these
> topics as well, including Andres Freund, Kyotaro Horiguchi, and
> probably some folks at 2ndQuadrant (but I don't know exactly who).

> 1. asynchronous execution
>

Not looking at that.

> 2. vectorized execution...

> We might also want to consider storing batches of tuples in a
> column-optimized
> rather than row-optimized format so that iterating through one or two
> attributes across every tuple in the batch touches the minimal number
> of cache lines.
>

Team is about 2 years into research and coding prototype on those topics at
this point, with agreed time for further work over next 2 years.

I'll let my colleagues chime in with details since I'm not involved at that
level any more.

--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-05-09 19:46:45 GIN logging GIN_SEGMENT_UNMODIFIED actions?
Previous Message Sherrylyn Branchaw 2016-05-09 17:42:48 Re: Change error code for hstore syntax error