On 09/18/2013 09:19 PM, Dimitri Fontaine wrote: > Kevin Grittner <kgri...@ymail.com> writes: >> change, but if '1.4' was stored in a column copied into a matview >> and they later updated the source to '1.40' the increase in >> accuracy would not flow to the matview. That would be a bug, not a >> feature. > Maybe the answer to that use case is to use the seg extension? > > http://www.postgresql.org/docs/9.3/interactive/seg.html > > IOW, colour me unconvinced about that binary-equality opclass use case > in MatViews. We are trusting the btree equality operator about > everywhere in PostgreSQL and it's quite disturbing to be told that in > fact we should not trust it. The problem is, that in this case the simple VIEW and MATVIEW would yield different results.
-- Hannu Krosing PostgreSQL Consultant Performance, Scalability and High Availability 2ndQuadrant Nordic OÜ -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
