There is currently a discussion[1] of creating a 2D matrix data type for
Postgres. This was motivated by a desire to add GPU support to the
Postgres kNN implementation. At it's foundation though, I think this is
an example of the problems with how Postgres arrays are implemented.
I've tried to raise visibility to some of the issues MADlib has run into
with Postgres arrays, but I have a very limited understanding of what
those problems are. I think it would be very useful for both communities
if some of you would chime in on that thread.
[1]
https://www.postgresql.org/message-id/flat/9A28C8860F777E439AA12E8AEA7694F8011F52EF%40BPXM15GP.gisp.nec.co.jp#[email protected]
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532) mobile: 512-569-9461
