Movatterモバイル変換

[0]ホーム
URL:

Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

 Sign up
Appearance settings

Commit47f9783

Browse files
committed
Changed product name throughout the documentation. Use value from the configure.
1 parentf24c625 commit47f9783

File tree

319 files changed

+2299
-2297
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

319 files changed

+2299
-2297
lines changed

‎doc/src/sgml/Makefile‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -143,6 +143,7 @@ version.sgml: $(top_srcdir)/configure
143143
{ \
144144
echo"<!ENTITY version\"$(VERSION)\">";\
145145
echo"<!ENTITY majorversion\"$(MAJORVERSION)\">";\
146+
echo"<!ENTITY productname\"$(PACKAGE_NAME)\">";\
146147
}>$@
147148

148149
features-supported.sgml:$(top_srcdir)/src/backend/catalog/sql_feature_packages.txt$(top_srcdir)/src/backend/catalog/sql_features.txt

‎doc/src/sgml/acronyms.sgml‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,8 +4,8 @@
44
<title>Acronyms</title>
55

66
<para>
7-
This is a list of acronyms commonly used in the <productname>PostgreSQL</>
8-
documentation and in discussions about <productname>PostgreSQL</>.
7+
This is a list of acronyms commonly used in the <productname>&productname;</>
8+
documentation and in discussions about <productname>&productname;</>.
99

1010
<variablelist>
1111

@@ -185,7 +185,7 @@
185185
<term><acronym>ECPG</acronym></term>
186186
<listitem>
187187
<para>
188-
<link linkend="ecpg">Embedded C forPostgreSQL</link>
188+
<link linkend="ecpg">Embedded C for&productname;</link>
189189
</para>
190190
</listitem>
191191
</varlistentry>
@@ -281,7 +281,7 @@
281281
<listitem>
282282
<para>
283283
<link linkend="config-setting">Grand Unified Configuration</link>,
284-
the <productname>PostgreSQL</> subsystem that handles server configuration
284+
the <productname>&productname;</> subsystem that handles server configuration
285285
</para>
286286
</listitem>
287287
</varlistentry>
@@ -476,7 +476,7 @@
476476
<term><acronym>PGSQL</acronym></term>
477477
<listitem>
478478
<para>
479-
<link linkend="postgres"><productname>PostgreSQL</></link>
479+
<link linkend="postgres"><productname>&productname;</></link>
480480
</para>
481481
</listitem>
482482
</varlistentry>
@@ -485,7 +485,7 @@
485485
<term><acronym>PGXS</acronym></term>
486486
<listitem>
487487
<para>
488-
<link linkend="extend-pgxs"><productname>PostgreSQL</> Extension System</link>
488+
<link linkend="extend-pgxs"><productname>&productname;</> Extension System</link>
489489
</para>
490490
</listitem>
491491
</varlistentry>

‎doc/src/sgml/advanced.sgml‎

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,10 +9,10 @@
99
<para>
1010
In the previous chapter we have covered the basics of using
1111
<acronym>SQL</acronym> to store and access your data in
12-
<productname>PostgreSQL</productname>. We will now discuss some
12+
<productname>&productname;</productname>. We will now discuss some
1313
more advanced features of <acronym>SQL</acronym> that simplify
1414
management and prevent loss or corruption of your data. Finally,
15-
we will look at some <productname>PostgreSQL</productname>
15+
we will look at some <productname>&productname;</productname>
1616
extensions.
1717
</para>
1818

@@ -93,7 +93,7 @@ SELECT * FROM myview;
9393
exists, and then inserting or rejecting the new
9494
<classname>weather</classname> records. This approach has a
9595
number of problems and is very inconvenient, so
96-
<productname>PostgreSQL</productname> can do this for you.
96+
<productname>&productname;</productname> can do this for you.
9797
</para>
9898

9999
<para>
@@ -216,7 +216,7 @@ UPDATE branches SET balance = balance + 100.00
216216
</para>
217217

218218
<para>
219-
In <productname>PostgreSQL</>, a transaction is set up by surrounding
219+
In <productname>&productname;</>, a transaction is set up by surrounding
220220
the SQL commands of the transaction with
221221
<command>BEGIN</> and <command>COMMIT</> commands. So our banking
222222
transaction would actually look like:
@@ -238,7 +238,7 @@ COMMIT;
238238
</para>
239239

240240
<para>
241-
<productname>PostgreSQL</> actually treats every SQL statement as being
241+
<productname>&productname;</> actually treats every SQL statement as being
242242
executed within a transaction. If you do not issue a <command>BEGIN</>
243243
command,
244244
then each individual statement has an implicit <command>BEGIN</> and
@@ -628,10 +628,10 @@ CREATE TABLE capitals (
628628
<structfield>population</>, and <structfield>altitude</>) from its
629629
<firstterm>parent</firstterm>, <classname>cities</classname>. The
630630
type of the column <structfield>name</structfield> is
631-
<type>text</type>, a native <productname>PostgreSQL</productname>
631+
<type>text</type>, a native <productname>&productname;</productname>
632632
type for variable length character strings. State capitals have
633633
an extra column, <structfield>state</>, that shows their state. In
634-
<productname>PostgreSQL</productname>, a table can inherit from
634+
<productname>&productname;</productname>, a table can inherit from
635635
zero or more other tables.
636636
</para>
637637

@@ -703,15 +703,15 @@ SELECT name, altitude
703703
<title>Conclusion</title>
704704

705705
<para>
706-
<productname>PostgreSQL</productname> has many features not
706+
<productname>&productname;</productname> has many features not
707707
touched upon in this tutorial introduction, which has been
708708
oriented toward newer users of <acronym>SQL</acronym>. These
709709
features are discussed in more detail in the remainder of this
710710
book.
711711
</para>
712712

713713
<para>
714-
If you feel you need more introductory material, please visit thePostgreSQL
714+
If you feel you need more introductory material, please visit the&productname;
715715
<ulink url="http://www.postgresql.org">web site</ulink>
716716
for links to more resources.
717717
</para>

‎doc/src/sgml/arch-dev.sgml‎

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
<!-- doc/src/sgml/arch-dev.sgml -->
22

33
<chapter id="overview">
4-
<title>Overview ofPostgreSQL Internals</title>
4+
<title>Overview of&productname; Internals</title>
55

66
<note>
77
<title>Author</title>
@@ -15,11 +15,11 @@
1515

1616
<para>
1717
This chapter gives an overview of the internal structure of the
18-
backend of <productname>PostgreSQL</productname>. After having
18+
backend of <productname>&productname;</productname>. After having
1919
read the following sections you should have an idea of how a query
2020
is processed. This chapter does not aim to provide a detailed
2121
description of the internal operation of
22-
<productname>PostgreSQL</productname>, as such a document would be
22+
<productname>&productname;</productname>, as such a document would be
2323
very extensive. Rather, this chapter is intended to help the reader
2424
understand the general sequence of operations that occur within the
2525
backend from the point at which a query is received, to the point
@@ -37,7 +37,7 @@
3737
<procedure>
3838
<step>
3939
<para>
40-
A connection from an application program to the <productname>PostgreSQL</productname>
40+
A connection from an application program to the <productname>&productname;</productname>
4141
server has to be established. The application program transmits a
4242
query to the server and waits to receive the results sent back by the
4343
server.
@@ -108,7 +108,7 @@
108108

109109
<para>
110110
In the following sections we will cover each of the above listed items
111-
in more detail to give a better understanding of <productname>PostgreSQL</productname>'s internal
111+
in more detail to give a better understanding of <productname>&productname;</productname>'s internal
112112
control and data structures.
113113
</para>
114114
</sect1>
@@ -117,7 +117,7 @@
117117
<title>How Connections are Established</title>
118118

119119
<para>
120-
<productname>PostgreSQL</productname> is implemented using a
120+
<productname>&productname;</productname> is implemented using a
121121
simple <quote>process per user</> client/server model. In this model
122122
there is one <firstterm>client process</firstterm> connected to
123123
exactly one <firstterm>server process</firstterm>. As we do not
@@ -135,7 +135,7 @@
135135

136136
<para>
137137
The client process can be any program that understands the
138-
<productname>PostgreSQL</productname> protocol described in
138+
<productname>&productname;</productname> protocol described in
139139
<xref linkend="protocol">. Many clients are based on the
140140
C-language library <application>libpq</>, but several independent
141141
implementations of the protocol exist, such as the Java
@@ -220,7 +220,7 @@
220220
<para>
221221
The mentioned transformations and compilations are normally done
222222
automatically using the <firstterm>makefiles</firstterm>
223-
shipped with the <productname>PostgreSQL</productname>
223+
shipped with the <productname>&productname;</productname>
224224
source distribution.
225225
</para>
226226
</note>
@@ -282,13 +282,13 @@
282282
</sect1>
283283

284284
<sect1 id="rule-system">
285-
<title>The <productname>PostgreSQL</productname> Rule System</title>
285+
<title>The <productname>&productname;</productname> Rule System</title>
286286

287287
<para>
288-
<productname>PostgreSQL</productname> supports a powerful
288+
<productname>&productname;</productname> supports a powerful
289289
<firstterm>rule system</firstterm> for the specification
290290
of <firstterm>views</firstterm> and ambiguous <firstterm>view updates</firstterm>.
291-
Originally the <productname>PostgreSQL</productname>
291+
Originally the <productname>&productname;</productname>
292292
rule system consisted of two implementations:
293293

294294
<itemizedlist>
@@ -346,7 +346,7 @@
346346
space. In particular, this occurs when executing queries
347347
involving large numbers of join operations. In order to determine
348348
a reasonable (not necessarily optimal) query plan in a reasonable amount
349-
of time, <productname>PostgreSQL</productname> uses a <firstterm>Genetic
349+
of time, <productname>&productname;</productname> uses a <firstterm>Genetic
350350
Query Optimizer</firstterm> (see <xref linkend="geqo">) when the number of joins
351351
exceeds a threshold (see <xref linkend="guc-geqo-threshold">).
352352
</para>

‎doc/src/sgml/array.sgml‎

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@
88
</indexterm>
99

1010
<para>
11-
<productname>PostgreSQL</productname> allows columns of a table to be
11+
<productname>&productname;</productname> allows columns of a table to be
1212
defined as variable-length multidimensional arrays. Arrays of any
1313
built-in or user-defined base type, enum type, or composite type
1414
can be created.
@@ -80,7 +80,7 @@ CREATE TABLE tictactoe (
8080
<programlisting>
8181
pay_by_quarter integer ARRAY,
8282
</programlisting>
83-
As before, however, <productname>PostgreSQL</> does not enforce the
83+
As before, however, <productname>&productname;</> does not enforce the
8484
size restriction in any case.
8585
</para>
8686
</sect2>
@@ -107,7 +107,7 @@ CREATE TABLE tictactoe (
107107
where <replaceable>delim</replaceable> is the delimiter character
108108
for the type, as recorded in its <literal>pg_type</literal> entry.
109109
Among the standard data types provided in the
110-
<productname>PostgreSQL</productname> distribution, all use a comma
110+
<productname>&productname;</productname> distribution, all use a comma
111111
(<literal>,</>), except for type <type>box</> which uses a semicolon
112112
(<literal>;</>). Each <replaceable>val</replaceable> is
113113
either a constant of the array element type, or a subarray. An example
@@ -221,7 +221,7 @@ SELECT name FROM sal_emp WHERE pay_by_quarter[1] &lt;&gt; pay_by_quarter[2];
221221
</programlisting>
222222

223223
The array subscript numbers are written within square brackets.
224-
By default <productname>PostgreSQL</productname> uses a
224+
By default <productname>&productname;</productname> uses a
225225
one-based numbering convention for arrays, that is,
226226
an array of <replaceable>n</> elements starts with <literal>array[1]</literal> and
227227
ends with <literal>array[<replaceable>n</>]</literal>.
@@ -682,7 +682,7 @@ SELECT array_positions(ARRAY[1, 4, 3, 1, 3, 4, 2, 1], 1);
682682
The delimiter character is usually a comma (<literal>,</>) but can be
683683
something else: it is determined by the <literal>typdelim</> setting
684684
for the array's element type. Among the standard data types provided
685-
in the <productname>PostgreSQL</productname> distribution, all use a comma,
685+
in the <productname>&productname;</productname> distribution, all use a comma,
686686
except for type <type>box</>, which uses a semicolon (<literal>;</>).
687687
In a multidimensional array, each dimension (row, plane,
688688
cube, etc.) gets its own level of curly braces, and delimiters
@@ -728,7 +728,7 @@ SELECT f1[1][-2][3] AS e1, f1[1][-1][5] AS e2
728728
variant), the element is taken to be NULL. The presence of any quotes
729729
or backslashes disables this and allows the literal string value
730730
<quote>NULL</> to be entered. Also, for backward compatibility with
731-
pre-8.2 versions of <productname>PostgreSQL</>, the <xref
731+
pre-8.2 versions of <productname>&productname;</>, the <xref
732732
linkend="guc-array-nulls"> configuration parameter can be turned
733733
<literal>off</> to suppress recognition of <literal>NULL</> as a NULL.
734734
</para>

0 commit comments

Comments
 (0)
[8]ページ先頭
©2009-2025 Movatter.jp