| From: | Perry Smith <pedzsan(at)gmail(dot)com> |
|---|---|
| To: | 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 21:27:53 |
| Message-ID: | C74C807F-508D-4807-9831-FCFB24E39C6D@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.
Thank you,
Perry
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert James | 2013-10-28 21:27:54 | pg_dump of only range of tables |
| Previous Message | Merlin Moncure | 2013-10-28 21:11:24 | Re: Cursor Example Needed |