On Mon, Apr 20, 2015 at 9:03 AM, Tomas Vondra <tomas.von...@2ndquadrant.com> wrote: > Sure, it's not an ultimate solution, but it might help a bit. I do have > other ideas how to optimize this, but in the planner every milisecond > counts. Looking at 'perf top' and seeing pglz_decompress() in top 3.
I suggested years ago that we should not compress data in pg_statistic. Tom shot that down, but I don't understand why. It seems to me that when we know data is extremely frequently accessed, storing it uncompressed makes sense. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers