From: | "Sander, Ingo (NSN - DE/Munich)" <ingo(dot)sander(at)nsn(dot)com> |
---|---|
To: | "ext Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>, "Merlin Moncure" <mmoncure(at)gmail(dot)com> |
Cc: | <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Runtime dependency from size of a bytea field |
Date: | 2010-10-06 05:39:26 |
Message-ID: | 9EB22E4572ECF74AAFEAE743C74D26B203A875F9@DEMUEXC005.nsn-intra.net |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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.
Ingo Sander
-----Original Message-----
From: ext Craig Ringer [mailto:craig(at)postnewspapers(dot)com(dot)au]
Sent: Wednesday, October 06, 2010 3:24 AM
To: Merlin Moncure
Cc: Sander, Ingo (NSN - DE/Munich); pgsql-performance(at)postgresql(dot)org
Subject: Re: [PERFORM] Runtime dependency from size of a bytea field
On 10/06/2010 12:11 AM, Merlin Moncure wrote:
> Probably you are hitting toast threshold and running into compression.
> compression you can disable, but toast you cannot (short of
> recompiling with higher blocksz).
For the OP's reference:
http://www.postgresql.org/docs/current/static/storage-toast.html
http://www.postgresql.org/docs/current/static/sql-altertable.html
While (I think) PLAIN storage could be used, the inability to span rows
over blocks means you would't get over 8k anyway.
--
Craig Ringer
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2010-10-06 12:51:03 | Re: Runtime dependency from size of a bytea field |
Previous Message | Craig Ringer | 2010-10-06 01:23:35 | Re: Runtime dependency from size of a bytea field |