diff --git a/doc/src/sgml/advanced.sgml b/doc/src/sgml/advanced.sgml index 79464fb89236d2b8a24adaa8ced4ff29d0a0ebd0..64ff4616e2d9fa7fa328ecac188232b63ea43f91 100644 --- a/doc/src/sgml/advanced.sgml +++ b/doc/src/sgml/advanced.sgml @@ -1,5 +1,5 @@ @@ -439,9 +439,9 @@ SELECT name, altitude indicates that the query should be run over only the cities table, and not tables below cities in the inheritance hierarchy. Many - of the commands that we have already discussed -- + of the commands that we have already discussed — SELECT, UPDATE, and - DELETE -- support this ONLY + DELETE — support this ONLY notation. diff --git a/doc/src/sgml/array.sgml b/doc/src/sgml/array.sgml index 7376034577c0485ab543984e7abe1d9628a92d1e..2307ad47fd55c1cb9a07545ac4032c445248befc 100644 --- a/doc/src/sgml/array.sgml +++ b/doc/src/sgml/array.sgml @@ -1,4 +1,4 @@ - + Arrays @@ -49,7 +49,7 @@ CREATE TABLE tictactoe ( However, the current implementation does not enforce the array size - limits --- the behavior is the same as for arrays of unspecified + limits — the behavior is the same as for arrays of unspecified length. diff --git a/doc/src/sgml/backup.sgml b/doc/src/sgml/backup.sgml index d1f25483df62bef569e50461861a4df2e83a6183..ef43d6877f39227524227396b398ecd2cc6b059d 100644 --- a/doc/src/sgml/backup.sgml +++ b/doc/src/sgml/backup.sgml @@ -1,5 +1,5 @@ Backup and Restore @@ -499,7 +499,7 @@ tar -cf backup.tar /usr/local/pgsql/data the administrator specify a shell command to be executed to copy a completed segment file to wherever it needs to go. The command could be as simple as a cp, or it could invoke a complex shell - script --- it's all up to you. + script — it's all up to you. @@ -725,7 +725,7 @@ SELECT pg_stop_backup(); last base backup, the interval between base backups should usually be chosen based on how much storage you want to expend on archived WAL files. You should also consider how long you are prepared to spend - recovering, if recovery should be necessary --- the system will have to + recovering, if recovery should be necessary — the system will have to replay all those WAL segments, and that could take awhile if it has been a long time since the last base backup. diff --git a/doc/src/sgml/catalogs.sgml b/doc/src/sgml/catalogs.sgml index e7cd4ec7e4a26bae1d3eed313f35c27eaf17fc13..f7335323fb46df80bab6cfcff759a631f9d5ce94 100644 --- a/doc/src/sgml/catalogs.sgml +++ b/doc/src/sgml/catalogs.sgml @@ -1,6 +1,6 @@ @@ -16,7 +16,7 @@ Normally, one should not change the system catalogs by hand, there are always SQL commands to do that. (For example, CREATE DATABASE inserts a row into the - pg_database catalog --- and actually + pg_database catalog — and actually creates the database on disk.) There are some exceptions for particularly esoteric operations, such as adding index access methods. @@ -2509,7 +2509,7 @@ not in its pg_opclass row, but in the associated rows in pg_amop and pg_amproc. Those rows are considered to be - part of the operator class definition --- this is not unlike the way + part of the operator class definition — this is not unlike the way that a relation is defined by a single pg_class row plus associated rows in pg_attribute and other tables. @@ -4275,7 +4275,7 @@ pg_stats is also designed to present the information in a more readable format than the underlying catalog - --- at the cost that its schema must be extended whenever new slot types + — at the cost that its schema must be extended whenever new slot types are defined for pg_statistic. diff --git a/doc/src/sgml/charset.sgml b/doc/src/sgml/charset.sgml index a3dc9c30f93825c0da165199480cb2305096b93b..ac2f184ec3c5ceea15f3663c6d701a55861a1b92 100644 --- a/doc/src/sgml/charset.sgml +++ b/doc/src/sgml/charset.sgml @@ -1,4 +1,4 @@ - + Localization</> @@ -829,12 +829,13 @@ RESET client_encoding; </para> <para> - If the conversion of a particular character is not possible -- - suppose you chose <literal>EUC_JP</literal> for the server and - <literal>LATIN1</literal> for the client, then some Japanese - characters cannot be converted to <literal>LATIN1</literal> -- it - is transformed to its hexadecimal byte values in parentheses, - e.g., <literal>(826C)</literal>. + If the conversion of a particular character is not possible + — suppose you chose <literal>EUC_JP</literal> for the + server and <literal>LATIN1</literal> for the client, then some + Japanese characters cannot be converted to + <literal>LATIN1</literal> — it is transformed to its + hexadecimal byte values in parentheses, e.g., + <literal>(826C)</literal>. </para> </sect2> diff --git a/doc/src/sgml/client-auth.sgml b/doc/src/sgml/client-auth.sgml index f96832df65290ff98957103f4a5e2e80e750e607..c88370b65fe01a2dd07f82be1d946be4245bd35e 100644 --- a/doc/src/sgml/client-auth.sgml +++ b/doc/src/sgml/client-auth.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.67 2004/11/10 21:54:23 petere Exp $ +$PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.68 2004/11/15 06:32:13 neilc Exp $ --> <chapter id="client-authentication"> @@ -14,7 +14,7 @@ $PostgreSQL: pgsql/doc/src/sgml/client-auth.sgml,v 1.67 2004/11/10 21:54:23 pete specifies which <productname>PostgreSQL</productname> user name it wants to connect as, much the same way one logs into a Unix computer as a particular user. Within the SQL environment the active database - user name determines access privileges to database objects -- see + user name determines access privileges to database objects — see <xref linkend="user-manag"> for more information. Therefore, it is essential to restrict which database users can connect. </para> diff --git a/doc/src/sgml/datetime.sgml b/doc/src/sgml/datetime.sgml index e037cf971800031f97020751588ebde6065d9565..6911a9863f73af04c70ef774391aa7f702e5d75b 100644 --- a/doc/src/sgml/datetime.sgml +++ b/doc/src/sgml/datetime.sgml @@ -1,5 +1,5 @@ <!-- -$PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.42 2004/08/10 00:55:03 tgl Exp $ +$PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.43 2004/11/15 06:32:13 neilc Exp $ --> <appendix id="datetime-appendix"> @@ -370,7 +370,7 @@ $PostgreSQL: pgsql/doc/src/sgml/datetime.sgml,v 2.42 2004/08/10 00:55:03 tgl Exp <xref linkend="datetime-timezone-input-table"> shows the time zone abbreviations recognized by <productname>PostgreSQL</productname> in date/time input values. Note that these names are <emphasis>not</> - used for date/time output --- display is driven by the currently + used for date/time output — display is driven by the currently selected <xref linkend="guc-timezone"> parameter setting. (It is likely that future releases will make some use of <varname>timezone</> for input as well.) diff --git a/doc/src/sgml/ddl.sgml b/doc/src/sgml/ddl.sgml index f50c6e478258379b03c5793f6a83d053167580a0..fcae34f4a50488c7c0717831ecc6502123ef80c6 100644 --- a/doc/src/sgml/ddl.sgml +++ b/doc/src/sgml/ddl.sgml @@ -1,4 +1,4 @@ -<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.31 2004/10/21 21:33:59 tgl Exp $ --> +<!-- $PostgreSQL: pgsql/doc/src/sgml/ddl.sgml,v 1.32 2004/11/15 06:32:13 neilc Exp $ --> <chapter id="ddl"> <title>Data Definition @@ -350,7 +350,7 @@ DROP TABLE products; identifiers are also 32-bit quantities. This creates a hard limit of 232 (4 billion) SQL commands within a single transaction. In practice this limit is not a - problem --- note that the limit is on number of + problem — note that the limit is on number of SQL commands, not number of rows processed. diff --git a/doc/src/sgml/dfunc.sgml b/doc/src/sgml/dfunc.sgml index 44e2f8287d4474a97f75a9c96445341a153bd84e..406112a3b84500bb84d0a658f44b71e0141aa85f 100644 --- a/doc/src/sgml/dfunc.sgml +++ b/doc/src/sgml/dfunc.sgml @@ -1,5 +1,5 @@ @@ -38,8 +38,8 @@ $PostgreSQL: pgsql/doc/src/sgml/dfunc.sgml,v 1.27 2003/11/29 19:51:36 pgsql Exp in memory when they are loaded by the executable. (Object files intended for executables are usually not compiled that way.) The command to link a shared library contains special flags to - distinguish it from linking an executable. --- At least this is the - theory. On some systems the practice is much uglier. + distinguish it from linking an executable (at least in theory + — on some systems the practice is much uglier). diff --git a/doc/src/sgml/docguide.sgml b/doc/src/sgml/docguide.sgml index 67b68195a87b4c36f48814bbf35a021a9ae049b5..92e06119ed12bd341d79ddbc15dfcb6c8ded8362 100644 --- a/doc/src/sgml/docguide.sgml +++ b/doc/src/sgml/docguide.sgml @@ -1,4 +1,4 @@ - + Documentation @@ -88,7 +88,7 @@ This is the definition of DocBook itself. We currently use version 4.2; you cannot use later or earlier versions. Note that there is also an XML version of DocBook - -- do not use that. + — do not use that. diff --git a/doc/src/sgml/errcodes.sgml b/doc/src/sgml/errcodes.sgml index 7bcff2c1d90870d8cb53e01e8961507eda7da2b7..bc900283f54674fa9e0af4137678ea23e53a80b8 100644 --- a/doc/src/sgml/errcodes.sgml +++ b/doc/src/sgml/errcodes.sgml @@ -1,4 +1,4 @@ - + <productname>PostgreSQL</productname> Error Codes @@ -125,7 +125,7 @@ Class 02 -No Data --- this is also a warning class per SQL99 +No Data — this is also a warning class per SQL99 diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index a34d255451eb4f127aa65e1e27bc994c0db49dbe..2549c516db9f8cf1a5822c1a273c7d77da01c3b7 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -1,5 +1,5 @@ @@ -2793,7 +2793,7 @@ substring('foobar' from '#"o_b#"%' for '#') NULLLIKE, pattern characters match string characters exactly unless they are special characters - in the regular expression language --- but regular expressions use + in the regular expression language — but regular expressions use different special characters than LIKE does. Unlike LIKE patterns, a regular expression is allowed to match anywhere within a string, unless @@ -8425,7 +8425,7 @@ SELECT relname FROM pg_class WHERE pg_table_is_visible(oid); SELECT pg_type_is_visible('myschema.widget'::regtype); Note that it would not make much sense to test an unqualified name in - this way --- if the name can be recognized at all, it must be visible. + this way — if the name can be recognized at all, it must be visible. diff --git a/doc/src/sgml/information_schema.sgml b/doc/src/sgml/information_schema.sgml index f1b3b672e1dd008b959650cc7e1770075a005497..4a2e8f581c5abd99537e1c68ae4192d5cd84d93d 100644 --- a/doc/src/sgml/information_schema.sgml +++ b/doc/src/sgml/information_schema.sgml @@ -1,4 +1,4 @@ - + The Information Schema @@ -11,7 +11,7 @@ The information schema consists of a set of views that contain information about the objects defined in the current database. The information schema is defined in the SQL standard and can therefore - be expected to be portable and remain stable --- unlike the system + be expected to be portable and remain stable — unlike the system catalogs, which are specific to PostgreSQL and are modelled after implementation concerns. The information schema views do not, diff --git a/doc/src/sgml/libpq.sgml b/doc/src/sgml/libpq.sgml index 3b58108be11f6d1735ad8b6632ee92575ce0b15c..05ffa373c047ca251d995dedc97e6d87926d1462 100644 --- a/doc/src/sgml/libpq.sgml +++ b/doc/src/sgml/libpq.sgml @@ -1,5 +1,5 @@ @@ -2252,7 +2252,7 @@ unsigned char *PQescapeBytea(const unsigned char *from, Converts an escaped string representation of binary data into binary - data --- the reverse of PQescapeBytea. + data — the reverse of PQescapeBytea. This is needed when retrieving bytea data in text format, but not when retrieving it in binary format. diff --git a/doc/src/sgml/maintenance.sgml b/doc/src/sgml/maintenance.sgml index 7d1dafad3182b74dc9f307746d5ead34258b050c..081c8fb697b7efeb8d72fc5509efdbc08183cd9b 100644 --- a/doc/src/sgml/maintenance.sgml +++ b/doc/src/sgml/maintenance.sgml @@ -1,5 +1,5 @@ @@ -117,7 +117,7 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.37 2004/08/05 23:32:10 tgl may be useful to set up periodic cron tasks that VACUUM only selected tables, skipping tables that are known not to change often. This is only likely to be helpful if you have both - large heavily-updated tables and large seldom-updated tables --- the + large heavily-updated tables and large seldom-updated tables — the extra cost of vacuuming a small table isn't enough to be worth worrying about. @@ -151,7 +151,7 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.37 2004/08/05 23:32:10 tgl The standard form of VACUUM is best used with the goal of maintaining a fairly level steady-state usage of disk space. If you need to return disk space to the operating system you can use - VACUUM FULL --- but what's the point of releasing disk + VACUUM FULL — but what's the point of releasing disk space that will only have to be allocated again soon? Moderately frequent standard VACUUM runs are a better approach than infrequent VACUUM FULL runs for maintaining @@ -278,7 +278,7 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.37 2004/08/05 23:32:10 tgl (32 bits at this writing) a cluster that runs for a long time (more than 4 billion transactions) will suffer transaction ID wraparound: the XID counter wraps around to zero, and all of a sudden - transactions that were in the past appear to be in the future --- which + transactions that were in the past appear to be in the future — which means their outputs become invisible. In short, catastrophic data loss. (Actually the data is still there, but that's cold comfort if you can't get at it.) @@ -337,7 +337,7 @@ $PostgreSQL: pgsql/doc/src/sgml/maintenance.sgml,v 1.37 2004/08/05 23:32:10 tgl is exactly one billion transactions: if you wait longer, it's possible that a row version that was not quite old enough to be reassigned last time is now more than two billion transactions old and has wrapped around - into the future --- i.e., is lost to you. (Of course, it'll reappear + into the future — i.e., is lost to you. (Of course, it'll reappear after another two billion transactions, but that's no help.) diff --git a/doc/src/sgml/mvcc.sgml b/doc/src/sgml/mvcc.sgml index e47d0094f24de049bd50253372c2dec39f836297..3b3b68a97fc76de5f14cb5c1ee2c21840b7d38f9 100644 --- a/doc/src/sgml/mvcc.sgml +++ b/doc/src/sgml/mvcc.sgml @@ -1,5 +1,5 @@ @@ -410,7 +410,7 @@ ERROR: could not serialize access due to concurrent update The intuitive meaning (and mathematical definition) of serializable execution is that any two successfully committed concurrent transactions will appear to have executed strictly serially, - one after the other --- although which one appeared to occur first may + one after the other — although which one appeared to occur first may not be predictable in advance. It is important to realize that forbidding the undesirable behaviors listed in is not sufficient to guarantee true serializability, and in fact @@ -524,7 +524,7 @@ SELECT SUM(value) FROM mytab WHERE class = 2; even if the name contains the word row; the names of the lock modes are historical. To some extent the names reflect the typical usage of each lock - mode --- but the semantics are all the same. The only real difference + mode — but the semantics are all the same. The only real difference between one lock mode and another is the set of lock modes with which each conflicts. Two transactions cannot hold locks of conflicting modes on the same table at the same time. (However, a transaction @@ -895,7 +895,7 @@ UPDATE accounts SET balance = balance - 100.00 WHERE acctnum = 22222; of transactions not counted by the first. Doing the two sums in a single serializable transaction will give an accurate picture of the effects of transactions that committed before the serializable transaction - started --- but one might legitimately wonder whether the answer is still + started — but one might legitimately wonder whether the answer is still relevant by the time it is delivered. If the serializable transaction itself applied some changes before trying to make the consistency check, the usefulness of the check becomes even more debatable, since now it diff --git a/doc/src/sgml/nls.sgml b/doc/src/sgml/nls.sgml index 70147fb6d0a68ce489746bceef2e4df4567bd299..55cd0f03ecfa0f6549c31d7405c0e1797fbb6e2f 100644 --- a/doc/src/sgml/nls.sgml +++ b/doc/src/sgml/nls.sgml @@ -1,5 +1,5 @@ @@ -18,7 +18,7 @@ $PostgreSQL: pgsql/doc/src/sgml/nls.sgml,v 1.9 2003/11/29 19:51:37 pgsql Exp $ PostgreSQL programs (server and client) can issue their messages in - your favorite language -- if the messages have been translated. + your favorite language — if the messages have been translated. Creating and maintaining translated message sets needs the help of people who speak their own language well and want to contribute to the PostgreSQL effort. You do not have to be a @@ -30,7 +30,7 @@ $PostgreSQL: pgsql/doc/src/sgml/nls.sgml,v 1.9 2003/11/29 19:51:37 pgsql Exp $ Requirements - We won't judge your language skills -- this section is about + We won't judge your language skills — this section is about software tools. Theoretically, you only need a text editor. But this is only in the unlikely event that you do not want to try out your translated messages. When you configure your source tree, be @@ -389,7 +389,7 @@ fprintf(stderr, gettext("panic level %d\n"), lvl); - List of provided translations -- empty in the beginning. + List of provided translations — initially empty. diff --git a/doc/src/sgml/perform.sgml b/doc/src/sgml/perform.sgml index 47792918ec6dad5b3d70537a6e5096bdd068ad25..6c23adb81b74ded7c47eb2cd301fad65d2024a0e 100644 --- a/doc/src/sgml/perform.sgml +++ b/doc/src/sgml/perform.sgml @@ -1,5 +1,5 @@ @@ -576,7 +576,7 @@ SELECT * FROM a CROSS JOIN b, c, d, e WHERE ...; both for reducing planning time and for directing the planner to a good query plan. If the planner chooses a bad join order by default, you can force it to choose a better order via JOIN syntax - --- assuming that you know of a better order, that is. Experimentation + — assuming that you know of a better order, that is. Experimentation is recommended. diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index d705920dcb04f90d52571bc86f872602d2151237..7221606d6ab7585fdc78ac876f53de966b923c47 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -1,5 +1,5 @@ @@ -129,7 +129,7 @@ $$ LANGUAGE plpgsql; a parameter as the name of a table or column in an SQL command. To get around this restriction, you can construct dynamic commands using the PL/pgSQL EXECUTE - statement --- at the price of constructing a new execution plan on + statement — at the price of constructing a new execution plan on every execution. @@ -499,7 +499,7 @@ $$ LANGUAGE plpgsql; control. PL/pgSQL's BEGIN/END are only for grouping; they do not start or end a transaction. Functions and trigger procedures are always executed within a transaction - established by an outer query --- they cannot start or commit that + established by an outer query — they cannot start or commit that transaction, since there would be no context for them to execute in. However, a block containing an EXCEPTION clause effectively forms a subtransaction that can be rolled back without affecting the @@ -2359,7 +2359,7 @@ RAISE EXCEPTION 'Nonexistent ID --> %', user_id; CREATE FUNCTION command, declaring it as a function with no arguments and a return type of trigger. Note that the function must be declared with no arguments even if it expects - to receive arguments specified in CREATE TRIGGER --- + to receive arguments specified in CREATE TRIGGER — trigger arguments are passed via TG_ARGV, as described below. diff --git a/doc/src/sgml/protocol.sgml b/doc/src/sgml/protocol.sgml index 41d49970234828123bb7a76c3263c986321618f2..15e03c3d3669473f2042729db03be98f67f8a52d 100644 --- a/doc/src/sgml/protocol.sgml +++ b/doc/src/sgml/protocol.sgml @@ -1,4 +1,4 @@ - + Frontend/Backend Protocol @@ -775,7 +775,7 @@ ErrorResponse, then reads and discards messages until a Sync is reached, then issues ReadyForQuery and returns to normal message processing. (But note that no skipping occurs if an error is detected - while processing Sync --- this ensures that there is one + while processing Sync — this ensures that there is one and only one ReadyForQuery sent for each Sync.) @@ -1034,7 +1034,7 @@ value changes for any of the parameters the backend believes the frontend should know about. Most commonly this occurs in response to a SET SQL command executed by the frontend, and - this case is effectively synchronous --- but it is also possible + this case is effectively synchronous — but it is also possible for parameter status changes to occur because the administrator changed a configuration file and then sent the SIGHUP signal to the postmaster. Also, @@ -1119,7 +1119,7 @@ - The cancellation signal may or may not have any effect --- for + The cancellation signal may or may not have any effect — for example, if it arrives after the backend has finished processing the query, then it will have no effect. If the cancellation is effective, it results in the current command being terminated diff --git a/doc/src/sgml/queries.sgml b/doc/src/sgml/queries.sgml index 7acc36b3788cf1c237c50ae5c8de3cecbcb4b15a..00659be9ef9dc1c4d7ac2f28a75b45be00218f01 100644 --- a/doc/src/sgml/queries.sgml +++ b/doc/src/sgml/queries.sgml @@ -1,4 +1,4 @@ - + Queries @@ -135,7 +135,7 @@ FROM table_reference , table_r not only that table but all of its subtable successors, unless the key word ONLY precedes the table name. However, the reference produces only the columns that appear in the named table - --- any columns added in subtables are ignored. + — any columns added in subtables are ignored. @@ -505,7 +505,7 @@ SELECT * FROM some_very_long_table_name s JOIN another_fairly_long_name a ON s.i The alias becomes the new name of the table reference for the - current query -- it is no longer possible to refer to the table + current query — it is no longer possible to refer to the table by the original name. Thus SELECT * FROM my_table AS m WHERE my_table.a > 5; diff --git a/doc/src/sgml/query.sgml b/doc/src/sgml/query.sgml index 245284346d5f7bba71a85b0728179b4923c3eb93..8240281b3d53ddea980df390a7ad77a265ddeb58 100644 --- a/doc/src/sgml/query.sgml +++ b/doc/src/sgml/query.sgml @@ -1,5 +1,5 @@ @@ -37,7 +37,7 @@ $PostgreSQL: pgsql/doc/src/sgml/query.sgml,v 1.39 2004/08/30 21:29:12 tgl Exp $ This creates the scripts and compiles the C files containing user-defined - functions and types. (You must use GNU make for this --- it may be named + functions and types. (You must use GNU make for this — it may be named something different on your system, often gmake.) Then, to start the tutorial, do the following: @@ -150,7 +150,7 @@ CREATE TABLE weather ( a type for storing single precision floating-point numbers. date should be self-explanatory. (Yes, the column of type date is also named date. - This may be convenient or confusing -- you choose.) + This may be convenient or confusing — you choose.) diff --git a/doc/src/sgml/ref/cluster.sgml b/doc/src/sgml/ref/cluster.sgml index 41e13fbbce226e9df4f87aeaee65e50cc4a984da..7cc0c2487e8495968c23524f27b8f146566f322d 100644 --- a/doc/src/sgml/ref/cluster.sgml +++ b/doc/src/sgml/ref/cluster.sgml @@ -1,5 +1,5 @@ @@ -159,7 +159,7 @@ CREATE TABLE newtable AS to rename newtable to the old name, and recreate the table's indexes. However, this approach does not preserve OIDs, constraints, foreign key relationships, granted privileges, and - other ancillary properties of the table --- all such items must be + other ancillary properties of the table — all such items must be manually recreated. diff --git a/doc/src/sgml/ref/copy.sgml b/doc/src/sgml/ref/copy.sgml index cc86af1ad16a3fd852bb194fcf9ec1dbeaeb8fff..5d7de053e76c2781ed3f41ad539494578883fca6 100644 --- a/doc/src/sgml/ref/copy.sgml +++ b/doc/src/sgml/ref/copy.sgml @@ -1,5 +1,5 @@ @@ -538,7 +538,7 @@ COPY tablename [ ( Signature -11-byte sequence PGCOPY\n\377\r\n\0 --- note that the zero byte +11-byte sequence PGCOPY\n\377\r\n\0 — note that the zero byte is a required part of the signature. (The signature is designed to allow easy identification of files that have been munged by a non-8-bit-clean transfer. This signature will be changed by end-of-line-translation @@ -638,7 +638,7 @@ distribution). If OIDs are included in the file, the OID field immediately follows the field-count word. It is a normal field except that it's not included -in the field-count. In particular it has a length word --- this will allow +in the field-count. In particular it has a length word — this will allow handling of 4-byte vs. 8-byte OIDs without too much pain, and will allow OIDs to be shown as null if that ever proves desirable. diff --git a/doc/src/sgml/ref/declare.sgml b/doc/src/sgml/ref/declare.sgml index ba00d6e29e69ea406836b12b1d4ddbc0f6e2cf2d..98dbd50adc5022f865cd3fabd40d54280f6872b8 100644 --- a/doc/src/sgml/ref/declare.sgml +++ b/doc/src/sgml/ref/declare.sgml @@ -1,5 +1,5 @@ @@ -78,7 +78,7 @@ DECLARE name [ BINARY ] [ INSENSITI specifies whether data is to be retrieved in text or binary format. This choice overrides the way that the cursor is defined. The concept of a binary cursor as such is thus obsolete when using extended query - protocol --- any cursor can be treated as either text or binary. + protocol — any cursor can be treated as either text or binary. diff --git a/doc/src/sgml/ref/lock.sgml b/doc/src/sgml/ref/lock.sgml index 34e01c82a58edab66938d4455e0dd9f26346b0d7..72a41c3c5ef9e242bdee291a2dea8b39f00f3dad 100644 --- a/doc/src/sgml/ref/lock.sgml +++ b/doc/src/sgml/ref/lock.sgml @@ -1,5 +1,5 @@ @@ -71,7 +71,7 @@ where lockmode is one of: TABLE statement before executing any data modification statement. A serializable transaction's view of data will be frozen when its first data modification statement begins. A later - LOCK TABLE will still prevent concurrent writes --- but it + LOCK TABLE will still prevent concurrent writes — but it won't ensure that what the transaction reads corresponds to the latest committed values. @@ -85,7 +85,7 @@ where lockmode is one of: mode, and then be unable to also acquire ROW EXCLUSIVE mode to actually perform their updates. (Note that a transaction's own locks never conflict, so a transaction can acquire ROW - EXCLUSIVE mode when it holds SHARE mode --- but not + EXCLUSIVE mode when it holds SHARE mode — but not if anyone else holds SHARE mode.) To avoid deadlocks, make sure all transactions acquire locks on the same objects in the same order, and if multiple lock modes are involved for a single diff --git a/doc/src/sgml/ref/postgres-ref.sgml b/doc/src/sgml/ref/postgres-ref.sgml index b0a5f920a9e10f67d6daa67a09cb8b8af22731e0..4baecaf2edac652b4a4ee5f6a9808c7607d6f3f7 100644 --- a/doc/src/sgml/ref/postgres-ref.sgml +++ b/doc/src/sgml/ref/postgres-ref.sgml @@ -1,5 +1,5 @@ @@ -393,7 +393,7 @@ PostgreSQL documentation SIGQUIT to terminate without the normal cleanup. These signals should not be used by users. It is also unwise to send SIGKILL to a postgres - process --- the postmaster will interpret this as + process — the postmaster will interpret this as a crash in postgres, and will force all the sibling postgres processes to quit as part of its standard crash-recovery procedure. diff --git a/doc/src/sgml/regress.sgml b/doc/src/sgml/regress.sgml index 2e70233551e03bbbc22ea131080400e2ffa663fc..ed772ffc81e1f544790c9d5e59be65ac28839aae 100644 --- a/doc/src/sgml/regress.sgml +++ b/doc/src/sgml/regress.sgml @@ -1,4 +1,4 @@ - + Regression Tests @@ -211,7 +211,7 @@ gmake installcheck fail if you run the test on the day of a daylight-saving time changeover, or the day after one. These queries expect that the intervals between midnight yesterday, midnight today and - midnight tomorrow are exactly twenty-four hours --- which is wrong + midnight tomorrow are exactly twenty-four hours — which is wrong if daylight-saving time went into or out of effect meanwhile. diff --git a/doc/src/sgml/rules.sgml b/doc/src/sgml/rules.sgml index d98661b45dab585dcfd2af0655d7d4db5d422f25..3c9aea3c43c53340f9e2e925843d88944a9f9920 100644 --- a/doc/src/sgml/rules.sgml +++ b/doc/src/sgml/rules.sgml @@ -1,4 +1,4 @@ - + The Rule System @@ -546,7 +546,7 @@ SELECT shoelace.sl_name, shoelace.sl_avail, the remaining range-table entries in the top query (in this example there are no more), and it will recursively check the range-table entries in the added subquery to see if any of them reference views. (But it - won't expand *OLD* or *NEW* --- otherwise we'd have infinite recursion!) + won't expand *OLD* or *NEW* — otherwise we'd have infinite recursion!) In this example, there are no rewrite rules for shoelace_data or unit, so rewriting is complete and the above is the final result given to the planner. diff --git a/doc/src/sgml/sources.sgml b/doc/src/sgml/sources.sgml index 61f61d40c200a22081fef9f3adfa5c284538fe2c..6745599579fe0c8a44c6caca7d6e12afc9f7b697 100644 --- a/doc/src/sgml/sources.sgml +++ b/doc/src/sgml/sources.sgml @@ -1,5 +1,5 @@ @@ -117,7 +117,7 @@ less -x4 error). The errcode call specifies the SQLSTATE error code using a macro defined in src/include/utils/errcodes.h. The errmsg call provides the primary message text. Notice the - extra set of parentheses surrounding the auxiliary function calls --- + extra set of parentheses surrounding the auxiliary function calls — these are annoying but syntactically necessary. diff --git a/doc/src/sgml/sql.sgml b/doc/src/sgml/sql.sgml index fc48f5933e8cfb6723377d55919e81fdabde1191..47b47e79757993202ebde61b32d7093305502c9d 100644 --- a/doc/src/sgml/sql.sgml +++ b/doc/src/sgml/sql.sgml @@ -1,5 +1,5 @@ @@ -1314,7 +1314,7 @@ SELECT COUNT(PNO) SQL allows one to partition the tuples of a table into groups. Then the - aggregate operators described above can be applied to the groups --- + aggregate operators described above can be applied to the groups — i.e. the value of the aggregate operator is no longer calculated over all the values of the specified column but over all values of a group. Thus the aggregate operator is evaluated separately for every diff --git a/doc/src/sgml/syntax.sgml b/doc/src/sgml/syntax.sgml index 99038b426926b7bdfc35e88978378283884af413..30e344f8a810fbedfdad6a9222ee2d5a97567c45 100644 --- a/doc/src/sgml/syntax.sgml +++ b/doc/src/sgml/syntax.sgml @@ -1,5 +1,5 @@ @@ -725,9 +725,10 @@ SELECT 5 ! - 6; SELECT 5 ! (- 6); - because the parser has no idea -- until it is too late -- that - ! is defined as a postfix operator, not an infix one. - To get the desired behavior in this case, you must write + because the parser has no idea — until it is too late + — that ! is defined as a postfix operator, + not an infix one. To get the desired behavior in this case, you + must write SELECT (5 !) - 6; @@ -1259,7 +1260,7 @@ sqrt(2) The first form of aggregate expression invokes the aggregate across all input rows for which the given expression yields a non-null value. (Actually, it is up to the aggregate function - whether to ignore null values or not --- but all the standard ones do.) + whether to ignore null values or not — but all the standard ones do.) The second form is the same as the first, since ALL is the default. The third form invokes the aggregate for all distinct non-null values of the expression found @@ -1546,7 +1547,7 @@ SELECT ROW(1,2.5,'this is a test'); By default, the value created by a ROW expression is of an anonymous record type. If necessary, it can be cast to a named - composite type --- either the rowtype of a table, or a composite type + composite type — either the rowtype of a table, or a composite type created with CREATE TYPE AS. An explicit cast may be needed to avoid ambiguity. For example: diff --git a/doc/src/sgml/wal.sgml b/doc/src/sgml/wal.sgml index 9888de01932de3140e9768e4de6f2f13fa82badd..0545ad6f30bcb6bdafc2fe27f29d86ca563eb437 100644 --- a/doc/src/sgml/wal.sgml +++ b/doc/src/sgml/wal.sgml @@ -1,4 +1,4 @@ - + Write-Ahead Logging (<acronym>WAL</acronym>) @@ -87,7 +87,7 @@ we simply install a prior physical backup of the database, and replay the WAL log just as far as the desired time. What's more, the physical backup doesn't have to be an instantaneous snapshot - of the database state --- if it is made over some period of time, + of the database state — if it is made over some period of time, then replaying the WAL log for that period will fix any internal inconsistencies. @@ -306,7 +306,7 @@ To deal with the case where pg_control is corrupted, we should support the possibility of scanning existing log - segments in reverse order -- newest to oldest -- in order to find the + segments in reverse order — newest to oldest — in order to find the latest checkpoint. This has not been implemented yet. pg_control is small enough (less than one disk page) that it is not subject to partial-write problems, and as of this writing diff --git a/doc/src/sgml/xaggr.sgml b/doc/src/sgml/xaggr.sgml index 9373eade7871763a51dc9a3f8bb5dc629d0803db..8cb093200383778d604e4e1bac543c1cdbc29810 100644 --- a/doc/src/sgml/xaggr.sgml +++ b/doc/src/sgml/xaggr.sgml @@ -1,5 +1,5 @@ @@ -67,7 +67,7 @@ SELECT complex_sum(a) FROM test_complex; The above definition of sum will return zero (the initial state condition) if there are no nonnull input values. - Perhaps we want to return null in that case instead --- the SQL standard + Perhaps we want to return null in that case instead — the SQL standard expects sum to behave that way. We can do this simply by omitting the initcond phrase, so that the initial state condition is null. Ordinarily this would mean that the sfunc diff --git a/doc/src/sgml/xfunc.sgml b/doc/src/sgml/xfunc.sgml index 1fb67ba467d9286337f6d0d708bdff7f01008356..231e4bcec74a06d5168f7e93f6eb88df80c8a8b9 100644 --- a/doc/src/sgml/xfunc.sgml +++ b/doc/src/sgml/xfunc.sgml @@ -1,5 +1,5 @@ @@ -702,7 +702,7 @@ CREATE FUNCTION square_root(double precision) RETURNS double precision compiled into dynamically loadable objects (also called shared libraries) and are loaded by the server on demand. The dynamic loading feature is what distinguishes C language functions - from internal functions --- the actual coding conventions + from internal functions — the actual coding conventions are essentially the same for both. (Hence, the standard internal function library is a rich source of coding examples for user-defined C functions.) @@ -1170,7 +1170,7 @@ memcpy(destination->data, buffer, 40); Calling Conventions Version 0 for C-Language Functions - We present the old style calling convention first --- although + We present the old style calling convention first — although this approach is now deprecated, it's easier to get a handle on initially. In the version-0 method, the arguments and result of the C function are just declared in normal C style, but being @@ -1971,7 +1971,7 @@ AttInMetadata *TupleDescGetAttInMetadata(TupleDesc tupdesc) if you plan to work with C strings. If you are writing a function returning set, you can save the results of these functions in the - FuncCallContext structure --- use the + FuncCallContext structure — use the tuple_desc or attinmeta field respectively. diff --git a/doc/src/sgml/xindex.sgml b/doc/src/sgml/xindex.sgml index ca655304f5a9adbc82d5f61f1e6d1aba8daea809..3e608941abb6bac0a6ab0036d67f84fb2bd09217 100644 --- a/doc/src/sgml/xindex.sgml +++ b/doc/src/sgml/xindex.sgml @@ -1,5 +1,5 @@ @@ -42,7 +42,7 @@ $PostgreSQL: pgsql/doc/src/sgml/xindex.sgml,v 1.36 2003/11/29 19:51:38 pgsql Exp PostgreSQL, but all index methods are described in pg_am. It is possible to add a new index method by defining the required interface routines and - then creating a row in pg_am --- but that is + then creating a row in pg_am — but that is far beyond the scope of this chapter. @@ -745,7 +745,7 @@ SELECT * FROM table WHERE integer_column < 4; Consider again the situation where we are storing in the index only the bounding box of a complex object such as a polygon. In this case there's not much value in storing the whole polygon in the index - entry --- we may as well store just a simpler object of type + entry — we may as well store just a simpler object of type box. This situation is expressed by the STORAGE option in CREATE OPERATOR CLASS: we'd write something like diff --git a/doc/src/sgml/xoper.sgml b/doc/src/sgml/xoper.sgml index ea954d3298b266f113b4c99131a845a1d19bd54b..a35d0c93c5cda4ab8d0026c4419b07ae0001e69e 100644 --- a/doc/src/sgml/xoper.sgml +++ b/doc/src/sgml/xoper.sgml @@ -1,5 +1,5 @@ @@ -132,7 +132,7 @@ SELECT (a + b) AS c FROM test_complex; tab2.y = tab1.x, because the index-scan machinery expects to see the indexed column on the left of the operator it is given. PostgreSQL will not simply - assume that this is a valid transformation --- the creator of the + assume that this is a valid transformation — the creator of the = operator must specify that it is valid, by marking the operator with commutator information.