mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: Use proper em and en dashes

Browse Source
This commit is contained in:
Peter Eisentraut 2019-10-25 20:23:44 +02:00
parent ee20152070
commit cbe63d02d0
24 changed files with 112 additions and 114 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/src/sgml/biblio.sgml
View File

@ -309,7 +309,7 @@ ssimkovi@ag.or.at
</biblioset>
<confgroup>
<conftitle>Eleventh International Conference on Data Engineering</conftitle>
<confdates>6-10 March 1995</confdates>
<confdates>6&ndash;10 March 1995</confdates>
<address>Taipeh, Taiwan</address>
</confgroup>
<pubsnumber>Cat. No.95CH35724</pubsnumber>
@ -318,7 +318,7 @@ ssimkovi@ag.or.at
<address>Los Alamitos, California</address>
</publisher>
<pubdate>1995</pubdate>
<pagenums>420-7</pagenums>
<pagenums>420&ndash;7</pagenums>
</biblioentry>
<biblioentry id="ston86">
@ -427,7 +427,7 @@ ssimkovi@ag.or.at
<biblioset relation="journal">
<title>SIGMOD Record 18(4)</title>
<date>Dec. 1989</date>
<pagenums>4-11</pagenums>
<pagenums>4&ndash;11</pagenums>
</biblioset>
</biblioentry>

4
doc/src/sgml/bki.sgml
View File

@ -385,8 +385,8 @@
To find an available OID for a new pre-loaded row, run the
script <filename>src/include/catalog/unused_oids</filename>.
It prints inclusive ranges of unused OIDs (e.g., the output
line <quote>45-900</quote> means OIDs 45 through 900 have not been
allocated yet). Currently, OIDs 1-9999 are reserved for manual
line <literal>45-900</literal> means OIDs 45 through 900 have not been
allocated yet). Currently, OIDs 1&ndash;9999 are reserved for manual
assignment; the <filename>unused_oids</filename> script simply looks
through the catalog headers and <filename>.dat</filename> files
to see which ones do not appear. You can also use

2
doc/src/sgml/brin.sgml
View File

@ -781,7 +781,7 @@ typedef struct BrinOpcInfo
</table>
<para>
Support function numbers 1-10 are reserved for the BRIN internal
Support function numbers 1 through 10 are reserved for the BRIN internal
functions, so the SQL level functions start with number 11. Support
function number 11 is the main function required to build the index.
It should accept two arguments with the same data type as the operator class,

2
doc/src/sgml/catalogs.sgml
View File

@ -9883,7 +9883,7 @@ SELECT * FROM pg_locks pl LEFT JOIN pg_prepared_xacts ppx
<entry><structfield>slot_type</structfield></entry>
<entry><type>text</type></entry>
<entry></entry>
<entry>The slot type - <literal>physical</literal> or <literal>logical</literal></entry>
<entry>The slot type: <literal>physical</literal> or <literal>logical</literal></entry>
</row>
<row>

32
doc/src/sgml/charset.sgml
View File

@ -1004,7 +1004,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Traditional Chinese</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-2</entry>
<entry>1&ndash;2</entry>
<entry><literal>WIN950</literal>, <literal>Windows950</literal></entry>
</row>
<row>
@ -1013,7 +1013,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Simplified Chinese</entry>
<entry>Yes</entry>
<entry>Yes</entry>
<entry>1-3</entry>
<entry>1&ndash;3</entry>
<entry></entry>
</row>
<row>
@ -1022,7 +1022,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Japanese</entry>
<entry>Yes</entry>
<entry>Yes</entry>
<entry>1-3</entry>
<entry>1&ndash;3</entry>
<entry></entry>
</row>
<row>
@ -1031,7 +1031,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Japanese</entry>
<entry>Yes</entry>
<entry>No</entry>
<entry>1-3</entry>
<entry>1&ndash;3</entry>
<entry></entry>
</row>
<row>
@ -1040,7 +1040,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Korean</entry>
<entry>Yes</entry>
<entry>Yes</entry>
<entry>1-3</entry>
<entry>1&ndash;3</entry>
<entry></entry>
</row>
<row>
@ -1049,7 +1049,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Traditional Chinese, Taiwanese</entry>
<entry>Yes</entry>
<entry>Yes</entry>
<entry>1-3</entry>
<entry>1&ndash;3</entry>
<entry></entry>
</row>
<row>
@ -1058,7 +1058,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Chinese</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-4</entry>
<entry>1&ndash;4</entry>
<entry></entry>
</row>
<row>
@ -1067,7 +1067,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Simplified Chinese</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-2</entry>
<entry>1&ndash;2</entry>
<entry><literal>WIN936</literal>, <literal>Windows936</literal></entry>
</row>
<row>
@ -1112,7 +1112,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Korean (Hangul)</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-3</entry>
<entry>1&ndash;3</entry>
<entry></entry>
</row>
<row>
@ -1229,7 +1229,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Multilingual Emacs</entry>
<entry>Yes</entry>
<entry>No</entry>
<entry>1-4</entry>
<entry>1&ndash;4</entry>
<entry></entry>
</row>
<row>
@ -1238,7 +1238,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Japanese</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-2</entry>
<entry>1&ndash;2</entry>
<entry><literal>Mskanji</literal>, <literal>ShiftJIS</literal>, <literal>WIN932</literal>, <literal>Windows932</literal></entry>
</row>
<row>
@ -1247,7 +1247,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Japanese</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-2</entry>
<entry>1&ndash;2</entry>
<entry></entry>
</row>
<row>
@ -1265,7 +1265,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry>Korean</entry>
<entry>No</entry>
<entry>No</entry>
<entry>1-2</entry>
<entry>1&ndash;2</entry>
<entry><literal>WIN949</literal>, <literal>Windows949</literal></entry>
</row>
<row>
@ -1274,7 +1274,7 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<entry><emphasis>all</emphasis></entry>
<entry>Yes</entry>
<entry>Yes</entry>
<entry>1-4</entry>
<entry>1&ndash;4</entry>
<entry><literal>Unicode</literal></entry>
</row>
<row>
@ -1390,8 +1390,8 @@ CREATE COLLATION ignore_accents (provider = icu, locale = 'und-u-ks-level1-kc-tr
<para>
The <literal>SQL_ASCII</literal> setting behaves considerably differently
from the other settings. When the server character set is
<literal>SQL_ASCII</literal>, the server interprets byte values 0-127
according to the ASCII standard, while byte values 128-255 are taken
<literal>SQL_ASCII</literal>, the server interprets byte values 0&ndash;127
according to the ASCII standard, while byte values 128&ndash;255 are taken
as uninterpreted characters. No encoding conversion will be done when
the setting is <literal>SQL_ASCII</literal>. Thus, this setting is not so
much a declaration that a specific encoding is in use, as a declaration

6
doc/src/sgml/datetime.sgml
View File

@ -167,7 +167,7 @@
<tip>
<para>
Gregorian years AD 1-99 can be entered by using 4 digits with leading
Gregorian years AD 1&ndash;99 can be entered by using 4 digits with leading
zeros (e.g., <literal>0099</literal> is AD 99).
</para>
</tip>
@ -671,9 +671,9 @@ $ <userinput>cal 9 1752</userinput>
calendar, unrelated to the Julian calendar though it is confusingly
named similarly to that calendar.
The Julian Date system was invented by the French scholar
Joseph Justus Scaliger (1540-1609)
Joseph Justus Scaliger (1540&ndash;1609)
and probably takes its name from Scaliger's father,
the Italian scholar Julius Caesar Scaliger (1484-1558).
the Italian scholar Julius Caesar Scaliger (1484&ndash;1558).
In the Julian Date system, each day has a sequential number, starting
from JD 0 (which is sometimes called <emphasis>the</emphasis> Julian Date).
JD 0 corresponds to 1 January 4713 BC in the Julian calendar, or

36
doc/src/sgml/ecpg.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/ecpg.sgml -->
<chapter id="ecpg">
<title><application>ECPG</application> - Embedded <acronym>SQL</acronym> in C</title>
<title><application>ECPG</application> &mdash; Embedded <acronym>SQL</acronym> in C</title>
<indexterm zone="ecpg"><primary>embedded SQL</primary><secondary>in C</secondary></indexterm>
<indexterm zone="ecpg"><primary>C</primary></indexterm>
@ -2989,7 +2989,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%d</literal> - is replaced by the day of the month as a
decimal number (01-31).
decimal number (01&ndash;31).
</para>
</listitem>
<listitem>
@ -3025,7 +3025,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%e</literal> - is replaced by the day of month as a decimal
number (1-31); single digits are preceded by a blank.
number (1&ndash;31); single digits are preceded by a blank.
</para>
</listitem>
<listitem>
@ -3044,13 +3044,13 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<para>
<literal>%g</literal> - is replaced by the same year as in
<literal>%G</literal>, but as a decimal number without century
(00-99).
(00&ndash;99).
</para>
</listitem>
<listitem>
<para>
<literal>%H</literal> - is replaced by the hour (24-hour clock) as a
decimal number (00-23).
decimal number (00&ndash;23).
</para>
</listitem>
<listitem>
@ -3061,37 +3061,37 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%I</literal> - is replaced by the hour (12-hour clock) as a
decimal number (01-12).
decimal number (01&ndash;12).
</para>
</listitem>
<listitem>
<para>
<literal>%j</literal> - is replaced by the day of the year as a
decimal number (001-366).
decimal number (001&ndash;366).
</para>
</listitem>
<listitem>
<para>
<literal>%k</literal> - is replaced by the hour (24-hour clock) as a
decimal number (0-23); single digits are preceded by a blank.
decimal number (0&ndash;23); single digits are preceded by a blank.
</para>
</listitem>
<listitem>
<para>
<literal>%l</literal> - is replaced by the hour (12-hour clock) as a
decimal number (1-12); single digits are preceded by a blank.
decimal number (1&ndash;12); single digits are preceded by a blank.
</para>
</listitem>
<listitem>
<para>
<literal>%M</literal> - is replaced by the minute as a decimal
number (00-59).
number (00&ndash;59).
</para>
</listitem>
<listitem>
<para>
<literal>%m</literal> - is replaced by the month as a decimal number
(01-12).
(01&ndash;12).
</para>
</listitem>
<listitem>
@ -3124,7 +3124,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%S</literal> - is replaced by the second as a decimal
number (00-60).
number (00&ndash;60).
</para>
</listitem>
<listitem>
@ -3146,19 +3146,19 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%U</literal> - is replaced by the week number of the year
(Sunday as the first day of the week) as a decimal number (00-53).
(Sunday as the first day of the week) as a decimal number (00&ndash;53).
</para>
</listitem>
<listitem>
<para>
<literal>%u</literal> - is replaced by the weekday (Monday as the
first day of the week) as a decimal number (1-7).
first day of the week) as a decimal number (1&ndash;7).
</para>
</listitem>
<listitem>
<para>
<literal>%V</literal> - is replaced by the week number of the year
(Monday as the first day of the week) as a decimal number (01-53).
(Monday as the first day of the week) as a decimal number (01&ndash;53).
If the week containing January 1 has four or more days in the new
year, then it is week 1; otherwise it is the last week of the
previous year, and the next week is week 1.
@ -3173,13 +3173,13 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%W</literal> - is replaced by the week number of the year
(Monday as the first day of the week) as a decimal number (00-53).
(Monday as the first day of the week) as a decimal number (00&ndash;53).
</para>
</listitem>
<listitem>
<para>
<literal>%w</literal> - is replaced by the weekday (Sunday as the
first day of the week) as a decimal number (0-6).
first day of the week) as a decimal number (0&ndash;6).
</para>
</listitem>
<listitem>
@ -3203,7 +3203,7 @@ int PGTYPEStimestamp_fmt_asc(timestamp *ts, char *output, int str_len, char *fmt
<listitem>
<para>
<literal>%y</literal> - is replaced by the year without century as a
decimal number (00-99).
decimal number (00&ndash;99).
</para>
</listitem>
<listitem>

68
doc/src/sgml/func.sgml
View File

@ -5331,7 +5331,7 @@ SELECT foo FROM regexp_split_to_table('the quick brown fox', '\s*') AS foo;
<para>
Numeric character-entry escapes specifying values outside the ASCII range
(0-127) have meanings dependent on the database encoding. When the
(0&ndash;127) have meanings dependent on the database encoding. When the
encoding is UTF-8, escape values are equivalent to Unicode code points,
for example <literal>\u1234</literal> means the character <literal>U+1234</literal>.
For other multibyte encodings, character-entry escapes usually just
@ -6263,59 +6263,59 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
<tbody>
<row>
<entry><literal>HH</literal></entry>
<entry>hour of day (01-12)</entry>
<entry>hour of day (01&ndash;12)</entry>
</row>
<row>
<entry><literal>HH12</literal></entry>
<entry>hour of day (01-12)</entry>
<entry>hour of day (01&ndash;12)</entry>
</row>
<row>
<entry><literal>HH24</literal></entry>
<entry>hour of day (00-23)</entry>
<entry>hour of day (00&ndash;23)</entry>
</row>
<row>
<entry><literal>MI</literal></entry>
<entry>minute (00-59)</entry>
<entry>minute (00&ndash;59)</entry>
</row>
<row>
<entry><literal>SS</literal></entry>
<entry>second (00-59)</entry>
<entry>second (00&ndash;59)</entry>
</row>
<row>
<entry><literal>MS</literal></entry>
<entry>millisecond (000-999)</entry>
<entry>millisecond (000&ndash;999)</entry>
</row>
<row>
<entry><literal>US</literal></entry>
<entry>microsecond (000000-999999)</entry>
<entry>microsecond (000000&ndash;999999)</entry>
</row>
<row>
<entry><literal>FF1</literal></entry>
<entry>tenth of second (0-9)</entry>
<entry>tenth of second (0&ndash;9)</entry>
</row>
<row>
<entry><literal>FF2</literal></entry>
<entry>hundredth of second (00-99)</entry>
<entry>hundredth of second (00&ndash;99)</entry>
</row>
<row>
<entry><literal>FF3</literal></entry>
<entry>millisecond (000-999)</entry>
<entry>millisecond (000&ndash;999)</entry>
</row>
<row>
<entry><literal>FF4</literal></entry>
<entry>tenth of a millisecond (0000-9999)</entry>
<entry>tenth of a millisecond (0000&ndash;9999)</entry>
</row>
<row>
<entry><literal>FF5</literal></entry>
<entry>hundredth of a millisecond (00000-99999)</entry>
<entry>hundredth of a millisecond (00000&ndash;99999)</entry>
</row>
<row>
<entry><literal>FF6</literal></entry>
<entry>microsecond (000000-999999)</entry>
<entry>microsecond (000000&ndash;999999)</entry>
</row>
<row>
<entry><literal>SSSS</literal>, <literal>SSSSS</literal></entry>
<entry>seconds past midnight (0-86399)</entry>
<entry>seconds past midnight (0&ndash;86399)</entry>
</row>
<row>
<entry><literal>AM</literal>, <literal>am</literal>,
@ -6399,7 +6399,7 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
</row>
<row>
<entry><literal>MM</literal></entry>
<entry>month number (01-12)</entry>
<entry>month number (01&ndash;12)</entry>
</row>
<row>
<entry><literal>DAY</literal></entry>
@ -6427,15 +6427,15 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
</row>
<row>
<entry><literal>DDD</literal></entry>
<entry>day of year (001-366)</entry>
<entry>day of year (001&ndash;366)</entry>
</row>
<row>
<entry><literal>IDDD</literal></entry>
<entry>day of ISO 8601 week-numbering year (001-371; day 1 of the year is Monday of the first ISO week)</entry>
<entry>day of ISO 8601 week-numbering year (001&ndash;371; day 1 of the year is Monday of the first ISO week)</entry>
</row>
<row>
<entry><literal>DD</literal></entry>
<entry>day of month (01-31)</entry>
<entry>day of month (01&ndash;31)</entry>
</row>
<row>
<entry><literal>D</literal></entry>
@ -6447,15 +6447,15 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
</row>
<row>
<entry><literal>W</literal></entry>
<entry>week of month (1-5) (the first week starts on the first day of the month)</entry>
<entry>week of month (1&ndash;5) (the first week starts on the first day of the month)</entry>
</row>
<row>
<entry><literal>WW</literal></entry>
<entry>week number of year (1-53) (the first week starts on the first day of the year)</entry>
<entry>week number of year (1&ndash;53) (the first week starts on the first day of the year)</entry>
</row>
<row>
<entry><literal>IW</literal></entry>
<entry>week number of ISO 8601 week-numbering year (01-53; the first Thursday of the year is in week 1)</entry>
<entry>week number of ISO 8601 week-numbering year (01&ndash;53; the first Thursday of the year is in week 1)</entry>
</row>
<row>
<entry><literal>CC</literal></entry>
@ -6471,11 +6471,11 @@ SELECT regexp_match('abc01234xyz', '(?:(.*?)(\d+)(.*)){1,1}');
</row>
<row>
<entry><literal>RM</literal></entry>
<entry>month in upper case Roman numerals (I-XII; I=January)</entry>
<entry>month in upper case Roman numerals (I&ndash;XII; I=January)</entry>
</row>
<row>
<entry><literal>rm</literal></entry>
<entry>month in lower case Roman numerals (i-xii; i=January)</entry>
<entry>month in lower case Roman numerals (i&ndash;xii; i=January)</entry>
</row>
<row>
<entry><literal>TZ</literal></entry>
@ -8006,7 +8006,7 @@ SELECT EXTRACT(CENTURY FROM TIMESTAMP '2001-02-16 20:38:40');
<listitem>
<para>
For <type>timestamp</type> values, the day (of the month) field
(1 - 31) ; for <type>interval</type> values, the number of days
(1&ndash;31) ; for <type>interval</type> values, the number of days
</para>
<screen>
@ -8017,8 +8017,6 @@ SELECT EXTRACT(DAY FROM INTERVAL '40 days 1 minute');
<lineannotation>Result: </lineannotation><computeroutput>40</computeroutput>
</screen>
</listitem>
</varlistentry>
@ -8061,7 +8059,7 @@ SELECT EXTRACT(DOW FROM TIMESTAMP '2001-02-16 20:38:40');
<term><literal>doy</literal></term>
<listitem>
<para>
The day of the year (1 - 365/366)
The day of the year (1&ndash;365/366)
</para>
<screen>
@ -8106,7 +8104,7 @@ SELECT to_timestamp(982384720.12);
<term><literal>hour</literal></term>
<listitem>
<para>
The hour field (0 - 23)
The hour field (0&ndash;23)
</para>
<screen>
@ -8217,7 +8215,7 @@ SELECT EXTRACT(MILLISECONDS FROM TIME '17:12:28.5');
<term><literal>minute</literal></term>
<listitem>
<para>
The minutes field (0 - 59)
The minutes field (0&ndash;59)
</para>
<screen>
@ -8232,8 +8230,8 @@ SELECT EXTRACT(MINUTE FROM TIMESTAMP '2001-02-16 20:38:40');
<listitem>
<para>
For <type>timestamp</type> values, the number of the month
within the year (1 - 12) ; for <type>interval</type> values,
the number of months, modulo 12 (0 - 11)
within the year (1&ndash;12) ; for <type>interval</type> values,
the number of months, modulo 12 (0&ndash;11)
</para>
<screen>
@ -8253,7 +8251,7 @@ SELECT EXTRACT(MONTH FROM INTERVAL '2 years 13 months');
<term><literal>quarter</literal></term>
<listitem>
<para>
The quarter of the year (1 - 4) that the date is in
The quarter of the year (1&ndash;4) that the date is in
</para>
<screen>
@ -17541,7 +17539,7 @@ SELECT * FROM pg_ls_dir('.') WITH ORDINALITY AS t(ls,n);
<row>
<entry><literal><function>pg_notification_queue_usage()</function></literal></entry>
<entry><type>double</type></entry>
<entry>fraction of the asynchronous notification queue currently occupied (0-1)</entry>
<entry>fraction of the asynchronous notification queue currently occupied (0&ndash;1)</entry>
</row>
<row>
@ -17827,7 +17825,7 @@ SET search_path TO <replaceable>schema</replaceable> <optional>, <replaceable>sc
to. <function>pg_notification_queue_usage</function> returns the
fraction of the total available space for notifications currently
occupied by notifications that are waiting to be processed, as a
<type>double</type> in the range 0-1.
<type>double</type> in the range 0&ndash;1.
See <xref linkend="sql-listen"/> and <xref linkend="sql-notify"/>
for more information.
</para>

28
doc/src/sgml/high-availability.sgml
View File

@ -1715,22 +1715,22 @@ if (!triggered)
<itemizedlist>
<listitem>
<para>
Query access - <command>SELECT</command>, <command>COPY TO</command>
Query access: <command>SELECT</command>, <command>COPY TO</command>
</para>
</listitem>
<listitem>
<para>
Cursor commands - <command>DECLARE</command>, <command>FETCH</command>, <command>CLOSE</command>
Cursor commands: <command>DECLARE</command>, <command>FETCH</command>, <command>CLOSE</command>
</para>
</listitem>
<listitem>
<para>
Parameters - <command>SHOW</command>, <command>SET</command>, <command>RESET</command>
Settings: <command>SHOW</command>, <command>SET</command>, <command>RESET</command>
</para>
</listitem>
<listitem>
<para>
Transaction management commands
Transaction management commands:
<itemizedlist>
<listitem>
<para>
@ -1758,13 +1758,13 @@ if (!triggered)
</listitem>
<listitem>
<para>
Plans and resources - <command>PREPARE</command>, <command>EXECUTE</command>,
Plans and resources: <command>PREPARE</command>, <command>EXECUTE</command>,
<command>DEALLOCATE</command>, <command>DISCARD</command>
</para>
</listitem>
<listitem>
<para>
Plugins and extensions - <command>LOAD</command>
Plugins and extensions: <command>LOAD</command>
</para>
</listitem>
<listitem>
@ -1783,7 +1783,7 @@ if (!triggered)
<itemizedlist>
<listitem>
<para>
Data Manipulation Language (DML) - <command>INSERT</command>,
Data Manipulation Language (DML): <command>INSERT</command>,
<command>UPDATE</command>, <command>DELETE</command>, <command>COPY FROM</command>,
<command>TRUNCATE</command>.
Note that there are no allowed actions that result in a trigger
@ -1795,7 +1795,7 @@ if (!triggered)
</listitem>
<listitem>
<para>
Data Definition Language (DDL) - <command>CREATE</command>,
Data Definition Language (DDL): <command>CREATE</command>,
<command>DROP</command>, <command>ALTER</command>, <command>COMMENT</command>.
This restriction applies even to temporary tables, because carrying
out these operations would require updating the system catalog tables.
@ -1848,7 +1848,7 @@ if (!triggered)
</listitem>
<listitem>
<para>
Two-phase commit commands - <command>PREPARE TRANSACTION</command>,
Two-phase commit commands: <command>PREPARE TRANSACTION</command>,
<command>COMMIT PREPARED</command>, <command>ROLLBACK PREPARED</command>
because even read-only transactions need to write WAL in the
prepare phase (the first phase of two phase commit).
@ -1856,7 +1856,7 @@ if (!triggered)
</listitem>
<listitem>
<para>
Sequence updates - <function>nextval()</function>, <function>setval()</function>
Sequence updates: <function>nextval()</function>, <function>setval()</function>
</para>
</listitem>
<listitem>
@ -2223,18 +2223,18 @@ LOG: database system is ready to accept read only connections
<itemizedlist>
<listitem>
<para>
Data Definition Language (DDL) - e.g. <command>CREATE INDEX</command>
Data Definition Language (DDL): e.g. <command>CREATE INDEX</command>
</para>
</listitem>
<listitem>
<para>
Privilege and Ownership - <command>GRANT</command>, <command>REVOKE</command>,
Privilege and Ownership: <command>GRANT</command>, <command>REVOKE</command>,
<command>REASSIGN</command>
</para>
</listitem>
<listitem>
<para>
Maintenance commands - <command>ANALYZE</command>, <command>VACUUM</command>,
Maintenance commands: <command>ANALYZE</command>, <command>VACUUM</command>,
<command>CLUSTER</command>, <command>REINDEX</command>
</para>
</listitem>
@ -2351,7 +2351,7 @@ LOG: database system is ready to accept read only connections
<para>
In normal (non-recovery) mode, if you issue <command>DROP USER</command> or <command>DROP ROLE</command>
for a role with login capability while that user is still connected then
nothing happens to the connected user - they remain connected. The user cannot
nothing happens to the connected user &mdash; they remain connected. The user cannot
reconnect however. This behavior applies in recovery also, so a
<command>DROP USER</command> on the primary does not disconnect that user on the standby.
</para>

2
doc/src/sgml/history.sgml
View File

@ -106,7 +106,7 @@
and trimmed in size by 25%. Many internal changes improved
performance and
maintainability. <productname>Postgres95</productname> release
1.0.x ran about 30-50% faster on the Wisconsin Benchmark compared
1.0.x ran about 30&ndash;50% faster on the Wisconsin Benchmark compared
to <productname>POSTGRES</productname>, Version 4.2. Apart from
bug fixes, the following were the major enhancements:

2
doc/src/sgml/isn.sgml
View File

@ -379,7 +379,7 @@ SELECT isbn13(id) FROM test;
<sect2>
<title>Author</title>
<para>
Germ&aacute;n M&eacute;ndez Bravo (Kronuz), 2004 - 2006
Germ&aacute;n M&eacute;ndez Bravo (Kronuz), 2004&ndash;2006
</para>
<para>

6
doc/src/sgml/legal.sgml
View File

@ -3,7 +3,7 @@
<date>2019</date>
<copyright>
<year>1996-2019</year>
<year>1996&ndash;2019</year>
<holder>The PostgreSQL Global Development Group</holder>
</copyright>
@ -11,12 +11,12 @@
<title>Legal Notice</title>
<para>
<productname>PostgreSQL</productname> is Copyright &copy; 1996-2019
<productname>PostgreSQL</productname> is Copyright &copy; 1996&ndash;2019
by the PostgreSQL Global Development Group.
</para>
<para>
<productname>Postgres95</productname> is Copyright &copy; 1994-5
<productname>Postgres95</productname> is Copyright &copy; 1994&ndash;5
by the Regents of the University of California.
</para>

2
doc/src/sgml/libpq.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/libpq.sgml -->
<chapter id="libpq">
<title><application>libpq</application> - C Library</title>
<title><application>libpq</application> &mdash; C Library</title>
<indexterm zone="libpq">
<primary>libpq</primary>

2
doc/src/sgml/planstats.sgml
View File

@ -112,7 +112,7 @@ WHERE tablename='tenk1' AND attname='unique1';
into equal frequency buckets, so all we have to do is locate the bucket
that our value is in and count <emphasis>part</emphasis> of it and
<emphasis>all</emphasis> of the ones before. The value 1000 is clearly in
the second bucket (993-1997). Assuming a linear distribution of
the second bucket (993&ndash;1997). Assuming a linear distribution of
values inside each bucket, we can calculate the selectivity as:
<programlisting>

2
doc/src/sgml/plperl.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/plperl.sgml -->
<chapter id="plperl">
<title>PL/Perl - Perl Procedural Language</title>
<title>PL/Perl &mdash; Perl Procedural Language</title>
<indexterm zone="plperl">
<primary>PL/Perl</primary>

2
doc/src/sgml/plpgsql.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/plpgsql.sgml -->
<chapter id="plpgsql">
<title><application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language</title>
<title><application>PL/pgSQL</application> &mdash; <acronym>SQL</acronym> Procedural Language</title>
<indexterm zone="plpgsql">
<primary>PL/pgSQL</primary>

2
doc/src/sgml/plpython.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/plpython.sgml -->
<chapter id="plpython">
<title>PL/Python - Python Procedural Language</title>
<title>PL/Python &mdash; Python Procedural Language</title>
<indexterm zone="plpython"><primary>PL/Python</primary></indexterm>
<indexterm zone="plpython"><primary>Python</primary></indexterm>

2
doc/src/sgml/pltcl.sgml
View File

@ -1,7 +1,7 @@
<!-- doc/src/sgml/pltcl.sgml -->
<chapter id="pltcl">
<title>PL/Tcl - Tcl Procedural Language</title>
<title>PL/Tcl &mdash; Tcl Procedural Language</title>
<indexterm zone="pltcl">
<primary>PL/Tcl</primary>

4
doc/src/sgml/ref/alter_table.sgml
View File

@ -569,8 +569,8 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
These forms control the application of row security policies belonging
to the table. If enabled and no policies exist for the table, then a
default-deny policy is applied. Note that policies can exist for a table
even if row level security is disabled - in this case, the policies will
NOT be applied and the policies will be ignored.
even if row level security is disabled. In this case, the policies will
<emphasis>not</emphasis> be applied and the policies will be ignored.
See also
<xref linkend="sql-createpolicy"/>.
</para>

4
doc/src/sgml/ref/copy.sgml
View File

@ -827,8 +827,8 @@ filters, dropped zero bytes, dropped high bits, or parity changes.)
are numbered from 0 (<acronym>LSB</acronym>) to 31 (<acronym>MSB</acronym>). Note that
this field is stored in network byte order (most significant byte first),
as are all the integer fields used in the file format. Bits
16-31 are reserved to denote critical file format issues; a reader
should abort if it finds an unexpected bit set in this range. Bits 0-15
16&ndash;31 are reserved to denote critical file format issues; a reader
should abort if it finds an unexpected bit set in this range. Bits 0&ndash;15
are reserved to signal backwards-compatible format issues; a reader
should simply ignore any unexpected bits set in this range. Currently
only one flag bit is defined, and the rest must be zero:

2
doc/src/sgml/ref/create_sequence.sgml
View File

@ -98,7 +98,7 @@ SELECT * FROM <replaceable>name</replaceable>;
Do not throw an error if a relation with the same name already exists.
A notice is issued in this case. Note that there is no guarantee that
the existing relation is anything like the sequence that would have
been created - it might not even be a sequence.
been created &mdash; it might not even be a sequence.
</para>
</listitem>
</varlistentry>

2
doc/src/sgml/ref/create_table.sgml
View File

@ -1348,7 +1348,7 @@ WITH ( MODULUS <replaceable class="parameter">numeric_literal</replaceable>, REM
we try to move long column values into TOAST tables, and is also the
target length we try to reduce the length below once toasting begins.
This only affects columns marked as either External or Extended
and applies only to new tuples - there is no effect on existing rows.
and applies only to new tuples; there is no effect on existing rows.
By default this parameter is set to allow at least 4 tuples per block,
which with the default blocksize will be 2040 bytes. Valid values are
between 128 bytes and the (blocksize - header), by default 8160 bytes.

6
doc/src/sgml/syntax.sgml
View File

@ -392,7 +392,7 @@ SELECT 'foo' 'bar';
<literal>\<replaceable>o</replaceable></literal>,
<literal>\<replaceable>oo</replaceable></literal>,
<literal>\<replaceable>ooo</replaceable></literal>
(<replaceable>o</replaceable> = 0 - 7)
(<replaceable>o</replaceable> = 0&ndash;7)
</entry>
<entry>octal byte value</entry>
</row>
@ -400,7 +400,7 @@ SELECT 'foo' 'bar';
<entry>
<literal>\x<replaceable>h</replaceable></literal>,
<literal>\x<replaceable>hh</replaceable></literal>
(<replaceable>h</replaceable> = 0 - 9, A - F)
(<replaceable>h</replaceable> = 0&ndash;9, A&ndash;F)
</entry>
<entry>hexadecimal byte value</entry>
</row>
@ -408,7 +408,7 @@ SELECT 'foo' 'bar';
<entry>
<literal>\u<replaceable>xxxx</replaceable></literal>,
<literal>\U<replaceable>xxxxxxxx</replaceable></literal>
(<replaceable>x</replaceable> = 0 - 9, A - F)
(<replaceable>x</replaceable> = 0&ndash;9, A&ndash;F)
</entry>
<entry>16 or 32-bit hexadecimal Unicode character value</entry>
</row>

2
doc/src/sgml/textsearch.sgml
View File

@ -2253,7 +2253,7 @@ SELECT alias, description, token FROM ts_debug('http://example.com/stuff/index.h
<listitem>
<para>
Linguistic - Ispell dictionaries try to reduce input words to a
Linguistic &mdash; Ispell dictionaries try to reduce input words to a
normalized form; stemmer dictionaries remove word endings
</para>
</listitem>