| From: | Edson Richter <edsonrichter(at)hotmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Compressed binary field |
| Date: | 2012-09-10 23:04:28 |
| Message-ID: | BLU0-SMTP34851B26A14510A151EC158CFAC0@phx.gbl |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Em 10/09/2012 19:06, Kevin Grittner escreveu:
> Edson Richter <edsonrichter(at)hotmail(dot)com> wrote:
>
>> this automatic compression applies to bytea fields?
>
> Yes, but keep in mind that anything which is already compressed or
> encrypted will probably not compress much if at all. Many of the
> binary objects you might want to store in the database probably
> already use compression internally.
>
> -Kevin
My files are mostly XML, TXT and PDF files only.
I already have separate tables for storing files, and avoid to query
them together with other stuff.
So, should I use
alter table MYTABLE set storage EXTENDED
?
Thanks,
Edson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mike Christensen | 2012-09-11 00:27:54 | Bad pg_dump error message |
| Previous Message | Jeff Janes | 2012-09-10 23:03:44 | Re: checkpoint_timeout and archive_timeout |