array behavior

From: amit sehas <cun23(at)yahoo(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: array behavior
Date: 2011-12-15 22:15:53
Message-ID: 1323987353.93002.YahooMailClassic@web160504.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

If a field(attribute) in a type is declared to be an array. Then is it always the case that the array will be packed into a single tuple that resides in the database. There is the TOAST mechanism for oversized tuples but that is still considered to be a single tuple. Is there any circumstance in which an attribute which is an array will be broken up into individual
tuples which are somehow associated with the main tuple. Such as if the array happens to have 5000 elements and the tuple will become quite large if these are packed within a single tuple and additionally it may have undesirable performance impact if the queries are not even interested in seeing the array when fetching the object ?

thanks

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2011-12-15 23:37:18 Re: Moving more work outside WALInsertLock
Previous Message Andrew Dunstan 2011-12-15 21:47:30 Re: JSON for PG 9.2