Re: Recently noticed documentation issues

From: Amit Kapila <amit(dot)kapila(at)huawei(dot)com>
To: "'Craig Ringer'" <ringerc(at)ringerc(dot)id(dot)au>
Cc: "'PostgreSQL Hackers'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Recently noticed documentation issues
Date: 2012-08-24 14:06:59
Message-ID: 000601cd8201$ba8a5ae0$2f9f10a0$@kapila@huawei.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

From: Craig Ringer [mailto:ringerc(at)ringerc(dot)id(dot)au]
Sent: Friday, August 24, 2012 6:59 PM
On 08/24/2012 12:42 PM, Amit Kapila wrote:

>> 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

>Yes, but nowhere in:

> http://www.postgresql.org/docs/current/static/sql-fetch.html

> and IMO not clearly enough in the PL/PgSQL docs; it only appears in
> sample code.

Ref-cursors usage is also along with functions, so mentioning them along
with
PL/PgSQL docs looks more logical to me.
However in context of SQL statements also Fetch can use internally
generated cursor
names in quoted strings, so about that some description might be useful.
But again I
don't know clearly the usage of it, whether such kind of functionality is
used by
users or PG is expecting to get Fetch used in such contexts.

With Regards,
Amit Kapila.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-08-24 14:08:58 Re: pg_upgrade's exec_prog() coding improvement
Previous Message Craig Ringer 2012-08-24 13:29:09 Re: Recently noticed documentation issues