| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: alternative compression algorithms? |
| Date: | 2015-04-29 21:54:01 |
| Message-ID: | CA+Tgmob7oXE+P9SPj0+eRaLzWHPWL+DuWZ0qNAuGuHHNew2_xQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Apr 20, 2015 at 9:03 AM, Tomas Vondra
<tomas(dot)vondra(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2015-04-29 21:55:31 | Re: [COMMITTERS] pgsql: Add transforms feature |
| Previous Message | Robert Haas | 2015-04-29 21:50:15 | Re: Failure to coerce unknown type to specific type |