Fix some cross reference links.

This commit is contained in:
Peter Eisentraut 2000-12-26 00:10:37 +00:00
parent dccfd74935
commit fa1640aea0
7 changed files with 18 additions and 18 deletions

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.12 2000/12/22 18:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.13 2000/12/26 00:10:37 petere Exp $
--> -->
<chapter id="overview"> <chapter id="overview">
@ -284,7 +284,7 @@ select s.sname, se.pno
<para> <para>
Figure \ref{parsetree} shows the <firstterm>parse tree</firstterm> built by the Figure \ref{parsetree} shows the <firstterm>parse tree</firstterm> built by the
grammar rules and actions given in <filename>gram.y</filename> for the query grammar rules and actions given in <filename>gram.y</filename> for the query
given in <xref linkend="simple-select" endterm="simple-select"> given in <xref linkend="simple-select">
(without the <firstterm>operator tree</firstterm> for (without the <firstterm>operator tree</firstterm> for
the <firstterm>where clause</firstterm> which is shown in figure \ref{where_clause} the <firstterm>where clause</firstterm> which is shown in figure \ref{where_clause}
because there was not enough space to show both data structures in one because there was not enough space to show both data structures in one
@ -312,8 +312,8 @@ select s.sname, se.pno
<para> <para>
Figure \ref{where_clause} shows the operator tree built for the Figure \ref{where_clause} shows the operator tree built for the
where clause of the SQL query given in example where clause of the SQL query given in
<xref linkend="simple-select" endterm="simple-select"> <xref linkend="simple-select">
which is attached to the field which is attached to the field
<literal>qual</literal> of the <literal>SelectStmt</literal> node. The top node of the <literal>qual</literal> of the <literal>SelectStmt</literal> node. The top node of the
operator tree is an <literal>A_Expr</literal> node representing an <literal>AND</literal> operator tree is an <literal>A_Expr</literal> node representing an <literal>AND</literal>

View File

@ -39,9 +39,9 @@
within a cluster make calls to the library. within a cluster make calls to the library.
The library sends user requests over the network to the The library sends user requests over the network to the
<Application>postmaster</Application> <Application>postmaster</Application>
(<XRef LinkEnd="PGARCH-CONNECTIONS" EndTerm="PGARCH-CONNECTIONS">(a)), (<XRef LinkEnd="PGARCH-CONNECTIONS">(a)),
which in turn starts a new backend server process which in turn starts a new backend server process
(<XRef LinkEnd="PGARCH-CONNECTIONS" EndTerm="PGARCH-CONNECTIONS">(b)) (<XRef LinkEnd="PGARCH-CONNECTIONS">(b))
<Figure Id="PGARCH-CONNECTIONS"> <Figure Id="PGARCH-CONNECTIONS">
<Title>How a connection is established</Title> <Title>How a connection is established</Title>
@ -49,7 +49,7 @@ which in turn starts a new backend server process
</Figure> </Figure>
and connects the frontend process to the new server and connects the frontend process to the new server
(<XRef LinkEnd="PGARCH-CONNECTIONS" EndTerm="PGARCH-CONNECTIONS">(c)). (<XRef LinkEnd="PGARCH-CONNECTIONS">(c)).
From that point on, the frontend process and the backend From that point on, the frontend process and the backend
server communicate without intervention by the server communicate without intervention by the
<Application>postmaster</Application>. Hence, the <Application>postmaster</Application> is always running, waiting <Application>postmaster</Application>. Hence, the <Application>postmaster</Application> is always running, waiting

View File

@ -39,7 +39,7 @@
applications that wish to access a given database applications that wish to access a given database
within a cluster make calls to the library. within a cluster make calls to the library.
The library sends user requests over the network to the The library sends user requests over the network to the
<Application>postmaster</Application> (<XRef LinkEnd="ARCH-CLIENTSERVER" EndTerm="ARCH-CLIENTSERVER">), <Application>postmaster</Application> (<XRef LinkEnd="ARCH-CLIENTSERVER">),
which in turn starts a new backend server process which in turn starts a new backend server process
<Figure Id="ARCH-CLIENTSERVER"> <Figure Id="ARCH-CLIENTSERVER">

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.7 2000/11/29 20:15:59 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.8 2000/12/26 00:10:37 petere Exp $
--> -->
<chapter id="extend"> <chapter id="extend">
@ -196,7 +196,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/extend.sgml,v 1.7 2000/11/29 20:15:59 peter
The Reference Manual gives a more detailed explanation The Reference Manual gives a more detailed explanation
of these catalogs and their attributes. However, of these catalogs and their attributes. However,
<xref endterm="EXTEND-CATALOGS" linkend="EXTEND-CATALOGS"> <xref linkend="EXTEND-CATALOGS">
shows the major entities and their relationships shows the major entities and their relationships
in the system catalogs. (Attributes that do not refer in the system catalogs. (Attributes that do not refer
to other entities are not shown unless they are part of to other entities are not shown unless they are part of

View File

@ -1,9 +1,9 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.21 2000/12/22 18:57:49 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.22 2000/12/26 00:10:37 petere Exp $
--> -->
<chapter id="libpqplusplus"> <chapter id="libpqplusplus">
<title>libpq - C++ Binding Library</title> <title>libpq++ - C++ Binding Library</title>
<para> <para>
<filename>libpq++</filename> is the C++ API to <filename>libpq++</filename> is the C++ API to
@ -57,7 +57,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/Attic/libpq++.sgml,v 1.21 2000/12/22 18:57:
an application program: an application program:
<note> <note>
<para> <para>
Refer to the <xref endterm="libpq" linkend="libpq-envars"> for a complete Refer to <xref linkend="libpq-envars"> for a complete
list of available connection options. list of available connection options.
</para> </para>
</note> </note>

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.25 2000/12/22 18:57:50 petere Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/xfunc.sgml,v 1.26 2000/12/26 00:10:37 petere Exp $
--> -->
<chapter id="xfunc"> <chapter id="xfunc">
@ -342,7 +342,7 @@ SELECT clean_EMP();
There are currently three procedural languages available in the standard There are currently three procedural languages available in the standard
<productname>Postgres</productname> distribution (PLSQL, PLTCL and <productname>Postgres</productname> distribution (PLSQL, PLTCL and
PLPERL), and other languages can be defined. PLPERL), and other languages can be defined.
Refer to <xref linkend="xplang-title" endterm="xplang-title"> for Refer to <xref linkend="xplang"> for
more information. more information.
</para> </para>
</sect1> </sect1>
@ -1200,7 +1200,7 @@ LANGUAGE 'c';
it can be dynamically loaded into it can be dynamically loaded into
<productname>Postgres</productname> <productname>Postgres</productname>
always requires special flags. always requires special flags.
See <xref linkend="dfunc-title" endterm="dfunc-title"> See <xref linkend="dfunc">
for a detailed explanation of how to do it for for a detailed explanation of how to do it for
your particular operating system. your particular operating system.
</para> </para>

View File

@ -1,5 +1,5 @@
<!-- <!--
$Header: /cvsroot/pgsql/doc/src/sgml/xindex.sgml,v 1.11 2000/03/31 03:27:41 thomas Exp $ $Header: /cvsroot/pgsql/doc/src/sgml/xindex.sgml,v 1.12 2000/12/26 00:10:37 petere Exp $
Postgres documentation Postgres documentation
--> -->
@ -15,7 +15,7 @@ Postgres documentation
<para> <para>
Look back at Look back at
<xref endterm="EXTEND-CATALOGS" linkend="EXTEND-CATALOGS">. <xref linkend="EXTEND-CATALOGS">.
The right half shows the catalogs that we must modify in order to tell The right half shows the catalogs that we must modify in order to tell
<productname>Postgres</productname> how to use a user-defined type and/or <productname>Postgres</productname> how to use a user-defined type and/or
user-defined operators with an index (i.e., <filename>pg_am, pg_amop, user-defined operators with an index (i.e., <filename>pg_am, pg_amop,