On 8 May 2014 14:49, Stephen Frost <sfr...@snowman.net> wrote: > Your downthread comments on 'CREATE MATERIALIZED VIEW' are in the same > vein, though there I agree that we need it per-relation as there are > other trade-offs to consider (storage costs of the matview, cost to > maintain the matview, etc, similar to indexes). > > The PGStrom proposal, aiui, is to add a new join type which supports > using a GPU to answer a query where all the data is in regular PG > tables. I'd like that to "just work" when a GPU is available (perhaps > modulo having to install some extension), for any join which is costed > to be cheaper/faster when done that way.
All correct and agreed. As I explained earlier, lets cover the join requirement here and we can discuss lookasides to data structures at Pgcon. -- Simon Riggs http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
