From: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Compressed binary field |
Date: | 2012-09-10 19:09:24 |
Message-ID: | BLU0-SMTP16280A7F0AEAE01505C3055CFAC0@phx.gbl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Em 10/09/2012 15:35, Tom Lane escreveu:
> Edson Richter <edsonrichter(at)hotmail(dot)com> writes:
>> I would like to know if there is any plan to implement compressed fields
>> (just a "flag" in the field definition, like "not null") at database
>> side (these fields are and will never be indexed neither used for search).
> Any field value over a couple kilobytes is compressed automatically;
> this has been true for more than a dozen years. You can turn that
> off if you want, but it's done by default.
>
> http://www.postgresql.org/docs/9.1/static/storage-toast.html
>
> regards, tom lane
>
Hi, Tom!
I've read this section of manual, but I was wondering (problably I did
not fully understand the manual, maybe too technical or just my poor
english suffering here) if there is a way to force all these filed to be
compressed no matter size. I actually have more than 250,000 files in
database with 7Gb on size (about this amount every 6 months).
Thanks,
Edson
From | Date | Subject | |
---|---|---|---|
Next Message | Edson Richter | 2012-09-10 20:48:22 | Re: Compressed binary field |
Previous Message | Tom Lane | 2012-09-10 18:35:37 | Re: Compressed binary field |