Re: Runtime dependency from size of a bytea field - Mailing list pgsql-performance

From Sander, Ingo (NSN - DE/Munich)
Subject Re: Runtime dependency from size of a bytea field
Date
Msg-id 9EB22E4572ECF74AAFEAE743C74D26B203A87B87@DEMUEXC005.nsn-intra.net
Whole thread Raw
In response to Re: Runtime dependency from size of a bytea field  (Merlin Moncure <mmoncure@gmail.com>)
Responses Re: Runtime dependency from size of a bytea field  (Merlin Moncure <mmoncure@gmail.com>)
List 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@gmail.com]
Sent: Wednesday, October 06, 2010 2:51 PM
To: Sander, Ingo (NSN - DE/Munich)
Cc: ext Craig Ringer; pgsql-performance@postgresql.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.sander@nsn.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

pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Runtime dependency from size of a bytea field
Next
From: Merlin Moncure
Date:
Subject: Re: Runtime dependency from size of a bytea field