Re: where does postgres keep the query result until it is returned?

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Scott Ribe <scott_ribe(at)killerbytes(dot)com>
Cc: Willy-Bas Loos <willybas(at)gmail(dot)com>, pgsql-general Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: where does postgres keep the query result until it is returned?
Date: 2010-09-21 04:50:31
Message-ID: 4C983997.3090001@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 20/09/2010 10:56 PM, Scott Ribe wrote:

>> - should this be documented?
>
> Doubtful. It has to do with very well known limits of 32-bit programs, applies to any use for a 1GB block regardless of where it comes from (network or disk), really has nothing to do with postgres, and the actual size at which you'll start to have problems with vary a good bit depending on: OS, libraries you link to, memory management library you use, memory management techniques you use, and to a very great extent your specific app and exactly what it does.

If nothing else, it'd be helpful to mention in the docs that storage of
individual values requires a contiguous memory block for each value.
It's not unusual to have data structures that can be used to store large
amounts of data structured as linked lists of extent blocks, so this is
really a perfectly reasonable question to ask.

--
Craig Ringer

Tech-related writing at http://soapyfrogs.blogspot.com/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Marcus Engene 2010-09-21 09:40:51 varchar lengths
Previous Message John Cheng 2010-09-21 03:43:58 Re: Binary Replication and Slony