Re: Select count(*), the sequel

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



"Pierre C" <lists@xxxxxxxxxx> wrote:

in-page compression
How would that be different from the in-page compression done by
TOAST now?  Or are you just talking about being able to make it
more aggressive?
-Kevin

Well, I suppose lzo-style compression would be better used on data that is written a few times maximum and then mostly read (like a forum, data warehouse, etc). Then, good candidate pages for compression also probably have all tuples visible to all transactions, therefore all row headers would be identical and would compress very well. Of course this introduces a "small" problem for deletes and updates...

Delta compression is : take all the values for a column inside a page, look at the values and their statistical distribution, notice for example that they're all INTs and the values on the page fit between X+n and X-n, store X and only encode n with as few bits as possible for each row. This is only an example, the idea is to exploit the fact that on the same page, all the values of one column often have lots in common. xid values in row headers are a good example of this.

TOAST compresses datums, so it performs well on large datums ; this is the opposite, the idea is to compress small tuples by using the reduncancies between tuples.

--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux