Subject: Re: Regarding postgreSQL performance on DRAM
To: pgsql-admin@lists.postgresql.org
References: 
 <CADb0YNk+jYXt6oC3vefFzOigmG8WOCkXmeAq5L8ABA4eMbypHA@mail.gmail.com>
 <87va1exlfo.fsf@jsievers.enova.com>
From: Thomas Kellerer <spam_eater@gmx.net>
Message-ID: <f37b7ea7-966d-d54a-bf8d-a1c7229e5f8a@gmx.net>
Date: Wed, 20 Feb 2019 21:42:22 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de; rv:1.8.1.21)
 Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.5.666
MIME-Version: 1.0
In-Reply-To: <87va1exlfo.fsf@jsievers.enova.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: de-DE
Content-Transfer-Encoding: 8bit
Precedence: bulk

Jerry Sievers schrieb am 20.02.2019 um 21:19:
>> My workload is simple. I  insert 1 million rows into a table with 100
>> columns, where each column is 256 bytes in length, and every 10
>> inserts are batched into a transaction.
> 
> Your test workload qualifies for TOASTing due to the $unrealistically
> long physical tuple size.

Hmm. I though TOAST is only applied to single values, not the entire tuple (row)?

As each column is substantially shorter than the TOAST threshold, I would not expect toasting to kick in here.

Or am I missing something?