Re: [HACKERS] MAIN, Uncompressed? - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: [HACKERS] MAIN, Uncompressed?
Date
Msg-id CANP8+jKnuDPe0bQj3O_esqTBgTYHyipS2eGbPAeswBSDMGVXfQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] MAIN, Uncompressed?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] MAIN, Uncompressed?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 25 August 2017 at 12:24, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Simon Riggs <simon@2ndquadrant.com> writes:
>> It looks like we need a new Column Storage option for MAIN, Uncompressed.
>> We have these Column Storage options
>> Plain - inline only, uncompressed
>> Main - inline until external as last resort, compressible
>> External - external, uncompressed
>> Extended - external, compressible
>
>> So there is no option for Main, but not compressible...
>
> Doesn't Plain serve the purpose?

No, because that just gives an error if you try to insert a large column value.

> In point of fact, though, "never inline and never compress" is not really
> a useful option, as it can be more easily read as "fail on wide values".

Agreed, but that is not what I am proposing.

Main is roughly what is wanted, yet it always tries to compress. If
you already know that won't be useful it should be possible to turn
compression off.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] MAIN, Uncompressed?
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] MAIN, Uncompressed?