Re: Runtime dependency from size of a bytea field

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: "Sander, Ingo (NSN - DE/Munich)" <ingo(dot)sander(at)nsn(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: Runtime dependency from size of a bytea field
Date: 2010-10-06 01:23:35
Message-ID: 4CABCF97.1060903@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Sander, Ingo (NSN - DE/Munich) 2010-10-06 05:39:26 Re: Runtime dependency from size of a bytea field
Previous Message Jeff Davis 2010-10-05 21:05:17 Re: Error message in wal_log for Streaming replication