| From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
|---|---|
| To: | "Sander, Ingo (NSN - DE/Munich)" <ingo(dot)sander(at)nsn(dot)com> |
| Cc: | ext Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Runtime dependency from size of a bytea field |
| Date: | 2010-10-06 12:51:03 |
| Message-ID: | AANLkTi=8Qji6Z+6AjbYATOCwLo32nF_CRppf5+pd7u36@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Oct 6, 2010 at 1:39 AM, Sander, Ingo (NSN - DE/Munich)
<ingo(dot)sander(at)nsn(dot)com> wrote:
> Changing of the storage method ( alter table bytea_demo Alter part1 Set
> storage EXTERNAL)
> or the increasing of the BLOCK_SIZE (new compilation of the code with
> --with-blocksize=32) change the behaviour.
yeah -- however changing block size is major surgery and is going to
have other effects (some of them negative) besides raising toast
threshold. I would start with disabling compression and see where you
stood on performance terms.
merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sander, Ingo (NSN - DE/Munich) | 2010-10-06 14:22:26 | Re: Runtime dependency from size of a bytea field |
| Previous Message | Sander, Ingo (NSN - DE/Munich) | 2010-10-06 05:39:26 | Re: Runtime dependency from size of a bytea field |