Re: Proposal: custom compression methods - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: Proposal: custom compression methods
Date
Msg-id 566E6F7E.8070508@anastigmatix.net
Whole thread Raw
In response to Re: Proposal: custom compression methods  (Craig Ringer <craig@2ndquadrant.com>)
Responses Re: Proposal: custom compression methods  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
On 12/14/15 01:50, Craig Ringer wrote:

> pg_upgrade means you can't just redefine the current toast bits so the
> compressed bit means "data is compressed, check first byte of varlena data
> for algorithm" because existing data won't have that, the first byte will
> be the start of the compressed data stream.

Is there any small sequence of initial bytes you wouldn't ever see in PGLZ
output?  Either something invalid, or something obviously nonoptimal
like run(n,'A')||run(n,'A') where PGLZ would have just output run(2n,'A')?

-Chap



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Declarative partitioning
Next
From: Victor Yegorov
Date:
Subject: Re: Disabling an index temporarily