Tom Lane wrote:
> Bruce Momjian <bruce@momjian.us> writes:
> > Tom Lane wrote:
> >> I still think that a link to the contrib module's page would be a good
> >> thing to provide here.
>
> > Yep, but how to do it in a clear way?
>
> The parenthetical wording we just discussed seemed fine to me.
OK, done with the attached patch.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
commit aa37baebccda661ab0edf9c6bf8498f1fd315152
Author: Bruce Momjian <bruce@momjian.us>
Date: Tue Jan 25 11:51:40 2011 -0500
Mention dblink module when mentioning dblink function.
diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml
index b995ff1..4160975 100644
*** /tmp/rbqvNe_queries.sgml Tue Jan 25 11:52:08 2011
--- /tmp/J4NBEe_queries.sgml Tue Jan 25 11:52:08 2011
*************** SELECT *
*** 686,692 ****
AS t1(proname name, prosrc text)
WHERE proname LIKE 'bytea%';
</programlisting>
! The <link linkend="CONTRIB-DBLINK-FUNCTION">dblink</> function executes
a remote query. It is declared to return
<type>record</> since it might be used for any kind of query.
The actual column set must be specified in the calling query so
--- 686,693 ----
AS t1(proname name, prosrc text)
WHERE proname LIKE 'bytea%';
</programlisting>
! The <link linkend="CONTRIB-DBLINK-FUNCTION">dblink</> function
! (part of the <link linkend="dblink">dblink</> module>) executes
a remote query. It is declared to return
<type>record</> since it might be used for any kind of query.
The actual column set must be specified in the calling query so