Re: Correct use of cursors for very large result sets in Postgres

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Correct use of cursors for very large result sets in Postgres
From: Mike Beaton <mjsbeaton@xxxxxxxxx>
Date: Sat, 18 Feb 2017 08:46:41 +0000
In-reply-to: <CAHzAAWQhQKsE2isFr6bGL-Q06CTQSg6Sjd_+Nt-4h9Gqu0aVHg@mail.gmail.com>
References: <CAHzAAWR4Hr8OQdjCuhDNsxTz3=qit4ufObSH=bJP9xxt2NLwLg@mail.gmail.com> <CAHzAAWRScAvevHu6AyK0ZZxnWo+SehXO9u51OSFvJEj9=61fXg@mail.gmail.com> <21063.1487349580@sss.pgh.pa.us> <CAHzAAWQhQKsE2isFr6bGL-Q06CTQSg6Sjd_+Nt-4h9Gqu0aVHg@mail.gmail.com>

I meant to say: "the `FETCH 10000 FROM cursor` until exhausted pattern will always be safe". Nasty typo, sorry!

References:
- Correct use of cursors for very large result sets in Postgres
  - From: Mike Beaton
- Re: Correct use of cursors for very large result sets in Postgres
  - From: Mike Beaton
- Re: Correct use of cursors for very large result sets in Postgres
  - From: Tom Lane
- Re: Correct use of cursors for very large result sets in Postgres
  - From: Mike Beaton

Prev by Date: Re: Correct use of cursors for very large result sets in Postgres
Next by Date: Re: Correct use of cursors for very large result sets in Postgres
Previous by thread: Re: Correct use of cursors for very large result sets in Postgres
Next by thread: Re: Correct use of cursors for very large result sets in Postgres
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux