From: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com> |
---|---|
To: | Perry Smith <pedzsan(at)gmail(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com> |
Cc: | PostgreSQL General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Cursor Example Needed |
Date: | 2013-10-28 22:21:31 |
Message-ID: | 526EE36B.1030302@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/28/2013 02:27 PM, Perry Smith wrote:
>
> On Oct 28, 2013, at 4:11 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>
>> On Mon, Oct 28, 2013 at 4:06 PM, Perry Smith <pedzsan(at)gmail(dot)com> wrote:
>>> When I execute the SELECT statement directly I get:
>>>
>>> psql:table.sql:28: out of memory for query result
>>
>> psql will do this automatically if you tell it to:
>> http://doginpool.blogspot.com/2011/11/retrieving-large-resultsets-from.html
>>
>> cursors can work with your code, but they need participation from the
>> client side. basically you stage the cursor then repeatedly FETCH
>> until done.
>
> Ok. I'll try that. I'm still curious how to do it using cursors if anyone wants
> to provide a sample.
http://www.postgresql.org/docs/9.3/interactive/sql-fetch.html
>
> Thank you,
> Perry
>
--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Perry Smith | 2013-10-28 22:49:46 | Re: Cursor Example Needed |
Previous Message | Adrian Klaver | 2013-10-28 22:01:18 | Re: pg_dump of only range of tables |