From: | "Sander, Ingo (NSN - DE/Munich)" <ingo(dot)sander(at)nsn(dot)com> |
---|---|
To: | "ext Merlin Moncure" <mmoncure(at)gmail(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 14:22:26 |
Message-ID: | 9EB22E4572ECF74AAFEAE743C74D26B203A87B87@DEMUEXC005.nsn-intra.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi,
I thougth I have disabled compressing by setting alter command? Or is
there another command?
BR
Ingo
-----Original Message-----
From: ext Merlin Moncure [mailto:mmoncure(at)gmail(dot)com]
Sent: Wednesday, October 06, 2010 2:51 PM
To: Sander, Ingo (NSN - DE/Munich)
Cc: ext Craig Ringer; pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Runtime dependency from size of a bytea field
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 | Merlin Moncure | 2010-10-06 14:49:53 | Re: Runtime dependency from size of a bytea field |
Previous Message | Merlin Moncure | 2010-10-06 12:51:03 | Re: Runtime dependency from size of a bytea field |