public inbox for [email protected]
help / color / mirror / Atom feedFrom: Josh Kupershmidt <[email protected]>
To: pgsql-docs <[email protected]>
Subject: broken index references
Date: Fri, 22 Mar 2013 20:03:50 -0700
Message-ID: <CAK3UJRGCsAuq_k1L=OXZm9SaETHcvkfnynRNn617Gu+fuX0pLg@mail.gmail.com> (raw)
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-docs>
If you search through recent 9.2 or 9.3dev PDFs for the string "??"
you should find ten occurrences. Other than the first instance in
Chapter 9, the other nine are all in the index, and indicate an
unknown reference to some index entry. For example, you can see in the
current 9.2-A4 PDF:
"""
deadlock, 349
timeout during, ??
...
fsync configuration parameter, ??
...
full_page_writes configuration parameter,
??
"""
AFAICT tex is getting confused by <indexterm> entries appearing before
<term>. Or at least, switching the order seems to fix the problem.
Patch attached.
Josh
--
Sent via pgsql-docs mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-docs
Attachments:
[application/octet-stream] fix_index_references.patch (6.1K, 2-fix_index_references.patch)
download | inline diff:
diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 6e1b084..93528d5 100644
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -1661,10 +1661,10 @@ include 'filename'
</varlistentry>
<varlistentry id="guc-fsync" xreflabel="fsync">
+ <term><varname>fsync</varname> (<type>boolean</type>)</term>
<indexterm>
<primary><varname>fsync</> configuration parameter</primary>
</indexterm>
- <term><varname>fsync</varname> (<type>boolean</type>)</term>
<listitem>
<para>
If this parameter is on, the <productname>PostgreSQL</> server
@@ -1846,10 +1846,10 @@ include 'filename'
</varlistentry>
<varlistentry id="guc-full-page-writes" xreflabel="full_page_writes">
+ <term><varname>full_page_writes</varname> (<type>boolean</type>)</term>
<indexterm>
<primary><varname>full_page_writes</> configuration parameter</primary>
</indexterm>
- <term><varname>full_page_writes</varname> (<type>boolean</type>)</term>
<listitem>
<para>
When this parameter is on, the <productname>PostgreSQL</> server
@@ -2920,6 +2920,7 @@ include 'filename'
<variablelist>
<varlistentry id="guc-geqo" xreflabel="geqo">
+ <term><varname>geqo</varname> (<type>boolean</type>)</term>
<indexterm>
<primary>genetic query optimization</primary>
</indexterm>
@@ -2930,7 +2931,6 @@ include 'filename'
<indexterm>
<primary><varname>geqo</> configuration parameter</primary>
</indexterm>
- <term><varname>geqo</varname> (<type>boolean</type>)</term>
<listitem>
<para>
Enables or disables genetic query optimization.
@@ -4972,6 +4972,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</varlistentry>
<varlistentry id="guc-default-transaction-isolation" xreflabel="default_transaction_isolation">
+ <term><varname>default_transaction_isolation</varname> (<type>enum</type>)</term>
<indexterm>
<primary>transaction isolation level</primary>
<secondary>setting default</secondary>
@@ -4979,7 +4980,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<indexterm>
<primary><varname>default_transaction_isolation</> configuration parameter</primary>
</indexterm>
- <term><varname>default_transaction_isolation</varname> (<type>enum</type>)</term>
+
<listitem>
<para>
Each SQL transaction has an isolation level, which can be
@@ -4998,6 +4999,7 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</varlistentry>
<varlistentry id="guc-default-transaction-read-only" xreflabel="default_transaction_read_only">
+ <term><varname>default_transaction_read_only</varname> (<type>boolean</type>)</term>
<indexterm>
<primary>read-only transaction</primary>
<secondary>setting default</secondary>
@@ -5006,7 +5008,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<primary><varname>default_transaction_read_only</> configuration parameter</primary>
</indexterm>
- <term><varname>default_transaction_read_only</varname> (<type>boolean</type>)</term>
<listitem>
<para>
A read-only SQL transaction cannot alter non-temporary tables.
@@ -5021,6 +5022,8 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
</varlistentry>
<varlistentry id="guc-default-transaction-deferrable" xreflabel="default_transaction_deferrable">
+ <term><varname>default_transaction_deferrable</varname> (<type>boolean</type>)</term>
+
<indexterm>
<primary>deferrable transaction</primary>
<secondary>setting default</secondary>
@@ -5029,7 +5032,6 @@ COPY postgres_log FROM '/full/path/to/logfile.csv' WITH csv;
<primary><varname>default_transaction_deferrable</> configuration parameter</primary>
</indexterm>
- <term><varname>default_transaction_deferrable</varname> (<type>boolean</type>)</term>
<listitem>
<para>
When running at the <literal>serializable</> isolation level,
@@ -5347,6 +5349,7 @@ SET XML OPTION { DOCUMENT | CONTENT };
</varlistentry>
<varlistentry id="guc-extra-float-digits" xreflabel="extra_float_digits">
+ <term><varname>extra_float_digits</varname> (<type>integer</type>)</term>
<indexterm>
<primary>significant digits</primary>
</indexterm>
@@ -5358,7 +5361,6 @@ SET XML OPTION { DOCUMENT | CONTENT };
<primary><varname>extra_float_digits</> configuration parameter</primary>
</indexterm>
- <term><varname>extra_float_digits</varname> (<type>integer</type>)</term>
<listitem>
<para>
This parameter adjusts the number of digits displayed for
@@ -5634,6 +5636,7 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
<variablelist>
<varlistentry id="guc-deadlock-timeout" xreflabel="deadlock_timeout">
+ <term><varname>deadlock_timeout</varname> (<type>integer</type>)</term>
<indexterm>
<primary>deadlock</primary>
<secondary>timeout during</secondary>
@@ -5646,7 +5649,6 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir'
<primary><varname>deadlock_timeout</> configuration parameter</primary>
</indexterm>
- <term><varname>deadlock_timeout</varname> (<type>integer</type>)</term>
<listitem>
<para>
This is the amount of time, in milliseconds, to wait on a lock
diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml
index 775d250..1a09c1c 100644
--- a/doc/src/sgml/libpq.sgml
+++ b/doc/src/sgml/libpq.sgml
@@ -2581,11 +2581,11 @@ char *PQresultErrorField(const PGresult *res, int fieldcode);
</varlistentry>
<varlistentry id="libpq-pg-diag-sqlstate">
+ <term><symbol>PG_DIAG_SQLSTATE</></term>
<indexterm>
<primary>error codes</primary>
<secondary>libpq</secondary>
</indexterm>
- <term><symbol>PG_DIAG_SQLSTATE</></term>
<listitem>
<para>
The SQLSTATE code for the error. The SQLSTATE code identifies
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected]
Subject: Re: broken index references
In-Reply-To: <CAK3UJRGCsAuq_k1L=OXZm9SaETHcvkfnynRNn617Gu+fuX0pLg@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox