From: | Rob Sargent <robjsargent(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: char array overhead |
Date: | 2014-03-31 17:09:59 |
Message-ID: | 5339A167.9000006@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 03/31/2014 09:48 AM, Steve Atkins wrote:
> On Mar 31, 2014, at 8:08 AM, Rob Sargent <robjsargent(at)gmail(dot)com> wrote:
>
>> I'm angling toward using a very wide char(1) array. Is the one-byte overhead for char(n<126) applied to each element or to the array?
> Each element, it's a variable length type.
>
> There's probably a better way of storing your data, but if you end up really needing a one-byte long character type, there is "char" (with the quotes).
>
> Cheers,
> Steve
>
>
>
Thank you! First for the confirmation on the overhead (how
disappointing) and secondly for the "char". That had not crossed my radar.
Jsyk, I'm toying with a rather large number of small valued datapoints
per sample. I'm tying text and smallint as well.
Thanks again,
rjs
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-03-31 18:07:34 | Re: char array overhead |
Previous Message | ethode | 2014-03-31 16:01:26 | Re: Alternative to Multi-Master Replication with 2 Data centers?? |