From: | Amit Kapila <amit(dot)kapila(at)huawei(dot)com> |
---|---|
To: | "'Craig Ringer'" <ringerc(at)ringerc(dot)id(dot)au>, "'PostgreSQL Hackers'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Recently noticed documentation issues |
Date: | 2012-08-24 04:42:50 |
Message-ID: | 001d01cd81b2$eb4594a0$c1d0bde0$@kapila@huawei.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
From: pgsql-hackers-owner(at)postgresql(dot)org
[mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Craig Ringer
Sent: Friday, August 24, 2012 7:17 AM
> I've recently noticed two oversights in the docs that I'd like to fix.
> First, in sql-fetch, there's no hint that the cursor name can be the
> quoted value of a refcursor, eg:
> FETCH ALL FROM "<unnamed portal 1>";
> This *is* shown in an example in plpgsql-cursors, but only in some
> sample code. If you set out with the question "how do I fetch the
> contents of a refcursor returned from a function" it's a lot harder to
> find the results than it could be.
Isn't what you are telling explained in Returning Cursors section on below
link:
http://www.postgresql.org/docs/9.1/static/plpgsql-cursors.html
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2012-08-24 04:44:14 | Re: plperl sigfpe reset can crash the server |
Previous Message | Amit Kapila | 2012-08-24 03:46:05 | Re: [WIP] Performance Improvement by reducing WAL for Update Operation |