> * Kouhei Kaigai (kai...@ak.jp.nec.com) wrote: > > > I didn't ask this before but it's been on my mind for a while- how > > > will this work for custom data types, ala the 'geometry' type from > PostGIS? > > > There's user-provided code that we have to execute to check equality > > > for those, but they're not giving us CUDA code to run to perform that > equality... > > > > > If custom-plan provider support the user-defined data types such as > > PostGIS, it will be able to pick up these data types also, in addition > > to built-in ones. It fully depends on coverage of the extension. > > If not a supported data type, it is not a show-time of GPUs. > > So the extension will need to be aware of all custom data types and then > installed *after* all other extensions are installed? That doesn't strike > me as workable... > I'm not certain why do you think an extension will need to support all the data types. Even if it works only for a particular set of data types, it makes sense as long as it covers data types user actually using.
Thanks, -- NEC OSS Promotion Center / PG-Strom Project KaiGai Kohei <kai...@ak.jp.nec.com> -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
