Takeshi Yamamuro <yamamuro(dot)takeshi(at)lab(dot)ntt(dot)co(dot)jp> writes:
> The attached is a patch to improve compression speeds with loss of
> compression ratios in backend/utils/adt/pg_lzcompress.c.

Why would that be a good tradeoff to make?  Larger stored values require
more I/O, which is likely to swamp any CPU savings in the compression
step.  Not to mention that a value once written may be read many times,
so the extra I/O cost could be multiplied many times over later on.

Another thing to keep in mind is that the compression area in general
is a minefield of patents.  We're fairly confident that pg_lzcompress
as-is doesn't fall foul of any, but any significant change there would
probably require more research.

			regards, tom lane

In response to

• Improve compression speeds in pg_lzcompress.c at 2013-01-07 07:29:58 from Takeshi Yamamuro

Responses

• Re: Improve compression speeds in pg_lzcompress.c at 2013-01-07 20:18:57 from Merlin Moncure
• Re: Improve compression speeds in pg_lzcompress.c at 2013-01-07 21:07:51 from Robert Haas

pgsql-hackers by date

Next:	From: Robert Haas	Date: 2013-01-07 16:57:27
	Subject: Re: ALTER .. OWNER TO error mislabels schema as other object type
Previous:	From: Merlin Moncure	Date: 2013-01-07 15:25:16
	Subject: Re: json api WIP patch