Re: Re: A separate table level option to control compression - Mailing list pgsql-hackers

From Shaun Thomas
Subject Re: Re: A separate table level option to control compression
Date
Msg-id CAG1YDPcX3-7ScKBj8dUOhSg4+0fqcwepCd6ON8ODuK8GWKyhMA@mail.gmail.com
Whole thread Raw
In response to Re: Re: A separate table level option to control compression  (Pavan Deolasee <pavan.deolasee@gmail.com>)
List pgsql-hackers
> Setting compress_tuple_target to a higher value won't be negative because the
> toast_tuple_target is used for compression anyways when compress_tuple_target
> is higher than toast_tuple_target.

Ack, you're right. Got my wires crossed. I must have gotten confused by my later
tests that enforced main storage and pushed out the toast tuple target
to prevent
out-of-line storage.

> I added a small discussion about negative effects of setting  compress_tuple_target
> lower though, per your suggestion.

Fair enough. I like the addition since it provides a very concrete
reason not to abuse
the parameter. :shipit:

Vaya con Queso

-- 
Shaun M Thomas - 2ndQuadrant
PostgreSQL Training, Services and Support
shaun.thomas@2ndquadrant.com | www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Raymond Martin
Date:
Subject: RE: minimizing pg_stat_statements performance overhead
Next
From: Tomas Vondra
Date:
Subject: Re: [HACKERS] PATCH: multivariate histograms and MCV lists