From: Björn Wittich <Bjoern_Wittich@gmx.de>
To: pgsql-performance@postgresql.org
Subject: Re: extremly bad select performance on huge table
Date: Fri, 24 Oct 2014 07:16:48 +0200
Message-ID: <5449E0C0.60904@gmx.de> (raw)
In-Reply-To: <5447C9A6.3000107@gmx.de>
References: <5446972B.9040409@gmx.de>
<9706.1413918462@sss.pgh.pa.us>
<5446B4B3.4030802@gmx.de>
<A76B25F2823E954C9E45E32FA49D70ECAB2FDEE5@mail.corp.perceptron.com>
<54473B2E.2080007@gmx.de>
<1413989639.83279.YahooMailNeo@web122306.mail.ne1.yahoo.com>
<5447C9A6.3000107@gmx.de>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Hi,
with a cursor the behaviour is the same. So I would like to ask a more
general question:
My client needs to receive data from a huge join. The time the client
waits for being able to fetch the first row is very long. When the
retrieval starts after about 10 mins, the client itself is I/O bound so
it is not able to catch up the elapsed time.
My workaround was to build a queue of small joins (assuming the huge
join delivers 10 mio rows I now have 10000 joins delivering 1000 rows ).
So the general question is: Is there a better solution then my crude
workaround?
Thank you
> Hi Kevin,
>
>
> this is what I need (I think). Hopefully a cursor can operate on a
> join. Will read docu now.
>
> Thanks!
>
>
> Björn
>
> Am 22.10.2014 16:53, schrieb Kevin Grittner:
>> Björn Wittich <Bjoern_Wittich@gmx.de> wrote:
>>
>>> I do not want the db server to prepare the whole query result at
>>> once, my intention is that the asynchronous retrieval starts as
>>> fast as possible.
>> Then you probably should be using a cursor.
>>
>> --
>> Kevin Grittner
>> EDB: http://www.enterprisedb.com
>> The Enterprise PostgreSQL Company
>>
>>
>
>
>
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: Bjoern_Wittich@gmx.de
Subject: Re: extremly bad select performance on huge table
In-Reply-To: <5449E0C0.60904@gmx.de>
* 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