From: Nick Matheson <Nick.D.Matheson@noaa.gov>
To: Andy Colson <andy@squeakycode.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Simple (hopefully) throughput question?
Date: Thu, 04 Nov 2010 14:38:23 +0000
Message-ID: <4CD2C55F.3040307@noaa.gov> (raw)
In-Reply-To: <4CD19E84.7070204@squeakycode.net>
References: <4CD1853F.2010800@noaa.gov>
<4CD19E84.7070204@squeakycode.net>
Andy-
> I have no idea if this would be helpful or not, never tried it, but
> when you fire off "select * from bigtable" pg will create the entire
> resultset in memory (and maybe swap?) and then send it all to the
> client in one big lump. You might try a cursor and fetch 100-1000 at
> a time from the cursor. No idea if it would be faster or slower.
I am pretty sure we have tried paged datasets and didn't see any
improvement. But we will put this on our list of things to double check,
better safe than sorry you know.
Thanks,
Nick
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Nick.D.Matheson@noaa.gov, andy@squeakycode.net
Subject: Re: Simple (hopefully) throughput question?
In-Reply-To: <4CD2C55F.3040307@noaa.gov>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox