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

Commit2475e87

Browse files
author
Thomas G. Lockhart
committed
Deprecate 'current' for date/time input.
Fix up references to "PostgreSQL" rather than "Postgres". Was roughly evenly split between the two before. ref/ files not yet done.
1 parenteec9511 commit2475e87

Some content is hidden

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

50 files changed

+2645
-2173
lines changed

‎doc/src/sgml/advanced.sgml‎

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.24 2001/11/19 23:17:38 tgl Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/advanced.sgml,v 1.25 2001/11/21 05:53:40 thomas Exp $
33
-->
44

55
<chapter id="tutorial-advanced">
@@ -215,7 +215,7 @@ UPDATE branches SET balance = balance + 100.00
215215
</para>
216216

217217
<para>
218-
In <productname>Postgres</>, a transaction is set up by surrounding
218+
In <productname>PostgreSQL</>, a transaction is set up by surrounding
219219
the SQL commands of the transaction with
220220
<command>BEGIN</> and <command>COMMIT</> commands. So our banking
221221
transaction would actually look like
@@ -233,7 +233,7 @@ COMMIT;
233233
</para>
234234

235235
<para>
236-
<productname>Postgres</> actually treats every SQL statement as being
236+
<productname>PostgreSQL</> actually treats every SQL statement as being
237237
executed within a transaction. If you don't issue a <command>BEGIN</>
238238
command,
239239
then each individual statement has an implicit <command>BEGIN</> and
@@ -316,7 +316,7 @@ CREATE TABLE capitals (
316316
<structfield>population</>, and <structfield>altitude</>) from its
317317
<firstterm>parent</firstterm>, <classname>cities</classname>. The
318318
type of the column <structfield>name</structfield> is
319-
<type>text</type>, a native <productname>Postgres</productname>
319+
<type>text</type>, a native <productname>PostgreSQL</productname>
320320
type for variable length character strings. State capitals have
321321
an extra column, state, that shows their state. In
322322
<productname>PostgreSQL</productname>, a table can inherit from

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

Lines changed: 22 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 petere Exp $
2+
$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.16 2001/11/21 05:53:40 thomas Exp $
33
-->
44

55
<chapter id="overview">
@@ -17,11 +17,11 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
1717

1818
<para>
1919
This chapter gives an overview of the internal structure of the
20-
backend of <productname>Postgres</productname>.
20+
backend of <productname>PostgreSQL</productname>.
2121
After having read the following sections you
2222
should have an idea of how a query is processed. Don't expect a
2323
detailed description here (I think such a description dealing with
24-
all data structures and functions used within <productname>Postgres</productname>
24+
all data structures and functions used within <productname>PostgreSQL</productname>
2525
would exceed 1000
2626
pages!). This chapter is intended to help understanding the general
2727
control and data flow within the backend from receiving a query to
@@ -39,7 +39,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
3939
<procedure>
4040
<step>
4141
<para>
42-
A connection from an application program to the <productname>Postgres</productname>
42+
A connection from an application program to the <productname>PostgreSQL</productname>
4343
server has to be established. The application program transmits a
4444
query to the server and receives the results sent back by the server.
4545
</para>
@@ -109,7 +109,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
109109

110110
<para>
111111
In the following sections we will cover every of the above listed items
112-
in more detail to give a better understanding on <productname>Postgres</productname>'s internal
112+
in more detail to give a better understanding on <productname>PostgreSQL</productname>'s internal
113113
control and data structures.
114114
</para>
115115
</sect1>
@@ -118,7 +118,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
118118
<title>How Connections are Established</title>
119119

120120
<para>
121-
<productname>Postgres</productname> is implemented using a simple "process per-user"
121+
<productname>PostgreSQL</productname> is implemented using a simple "process per-user"
122122
client/server model. In this model there is one <firstterm>client process</firstterm>
123123
connected to exactly one <firstterm>server process</firstterm>.
124124
As we don't know <foreignphrase>per se</foreignphrase>
@@ -142,7 +142,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
142142
interactive SQL queries) or any user application implemented using
143143
the <filename>libpg</filename> library. Note that applications implemented using
144144
<application>ecpg</application>
145-
(the <productname>Postgres</productname> embedded SQL preprocessor for C)
145+
(the <productname>PostgreSQL</productname> embedded SQL preprocessor for C)
146146
also use this library.
147147
</para>
148148

@@ -236,7 +236,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
236236
<para>
237237
The mentioned transformations and compilations are normally done
238238
automatically using the <firstterm>makefiles</firstterm>
239-
shipped with the <productname>Postgres</productname>
239+
shipped with the <productname>PostgreSQL</productname>
240240
source distribution.
241241
</para>
242242
</note>
@@ -255,7 +255,7 @@ $Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.15 2001/11/08 23:34:33 pe
255255

256256
<para>
257257
For a better understanding of the data structures used in
258-
<productname>Postgres</productname>
258+
<productname>PostgreSQL</productname>
259259
for the processing of a query we use an example to illustrate the
260260
changes made to these data structures in every stage.
261261
This example contains the following simple query that will be used in
@@ -443,13 +443,13 @@ current context are performed.
443443
</sect1>
444444

445445
<sect1 id="rule-system">
446-
<title>The <productname>Postgres</productname> Rule System</title>
446+
<title>The <productname>PostgreSQL</productname> Rule System</title>
447447

448448
<para>
449-
<productname>Postgres</productname> supports a powerful
449+
<productname>PostgreSQL</productname> supports a powerful
450450
<firstterm>rule system</firstterm> for the specification
451451
of <firstterm>views</firstterm> and ambiguous <firstterm>view updates</firstterm>.
452-
Originally the <productname>Postgres</productname>
452+
Originally the <productname>PostgreSQL</productname>
453453
rule system consisted of two implementations:
454454

455455
<itemizedlist>
@@ -459,7 +459,7 @@ current context are performed.
459459
implemented deep in the <firstterm>executor</firstterm>. The rule system was
460460
called whenever an individual tuple had been accessed. This
461461
implementation was removed in 1995 when the last official release
462-
of the <productname>Postgres</productname> project was transformed into
462+
of the <productname>PostgreSQL</productname> project was transformed into
463463
<productname>Postgres95</productname>.
464464
</para>
465465
</listitem>
@@ -478,7 +478,7 @@ current context are performed.
478478

479479
<para>
480480
For information on the syntax and creation of rules in the
481-
<productname>Postgres</productname> system refer to
481+
<productname>PostgreSQL</productname> system refer to
482482
<citetitle>The PostgreSQL User's Guide</citetitle>.
483483
</para>
484484

@@ -700,7 +700,7 @@ current context are performed.
700700
Another task performed by the planner/optimizer is fixing the
701701
<firstterm>operator ids</firstterm> in the <literal>Expr</literal>
702702
and <literal>Oper</literal> nodes. As
703-
mentioned earlier, <productname>Postgres</productname> supports a variety of different data
703+
mentioned earlier, <productname>PostgreSQL</productname> supports a variety of different data
704704
types and even user defined types can be used. To be able to maintain
705705
the huge amount of functions and operators it is necessary to store
706706
them in a system table. Each function and operator gets a unique
@@ -1181,7 +1181,7 @@ transformInsertStmt()} above have been added here as well.
11811181
\subsubsection{The Rewrite System}
11821182

11831183
This section describes the changes to the {\it rewrite system} of
1184-
<productname>Postgres</productname> that have been necessary to support the use of {\it views}
1184+
<productname>PostgreSQL</productname> that have been necessary to support the use of {\it views}
11851185
within queries using a {\it having clause} and to support the
11861186
definition of {\it views} by queries using a {\it having clause}.
11871187

@@ -1395,7 +1395,7 @@ items. Note that it is not necessary to understand the meaning of
13951395
every single source line here and therefore we will not discuss
13961396
detailed questions like "Why has the variable {\tt varno} to be
13971397
increased by 3?". Questions like that belong to a chapter dealing
1398-
with the implementation of {\it views} in <productname>Postgres</productname> and to be able to
1398+
with the implementation of {\it views} in <productname>PostgreSQL</productname> and to be able to
13991399
answer them it would be necessary to know all the functions and not
14001400
only those described here. The fact important for us is to make sure,
14011401
that whatever is applied to the {\it targetlist} and the data
@@ -1538,7 +1538,7 @@ examined.
15381538
%
15391539
<step> {\tt QueryRewrite()} \\
15401540
This function takes the {\it parsetree} of a query and rewrites it
1541-
using <productname>Postgres</productname>'s {\it rewrite system}. Before the query itself can be
1541+
using <productname>PostgreSQL</productname>'s {\it rewrite system}. Before the query itself can be
15421542
rewritten, subqueries that are possibly part of the query have to be
15431543
processed. Therefore the function {\tt QueryRewriteSubLink()} is
15441544
called for the {\it where clause} and for the {\it having clause}.
@@ -2750,7 +2750,7 @@ produced by the {\it parser stage} that can be executed by the {\it
27502750
executor}. In most cases there are several ways (paths) with different
27512751
cost to get to the same result. It's the {\it planner/optimizer's}
27522752
task to find out which path is the cheapest and to create a {\it plan}
2753-
using this path. The implementation of {\it unions} in <productname>Postgres</productname> is
2753+
using this path. The implementation of {\it unions} in <productname>PostgreSQL</productname> is
27542754
based on the following idea: \\
27552755
\\
27562756
The set derived by evaluating $A \cup B$ must contain every member of
@@ -2786,7 +2786,7 @@ and the sort is just performed to make its work easier.
27862786
\subsection{How Intersect, Except and Union Work Together}
27872787

27882788
The last section showed that every stage ({\it parser stage}, {\it
2789-
planner/optimizer}, {\it executor}) of <productname>Postgres</productname> has to provide
2789+
planner/optimizer}, {\it executor}) of <productname>PostgreSQL</productname> has to provide
27902790
features in order to support {\it union} statements. For the
27912791
implementation of {\it intersect} and {\it except} statements (and
27922792
statements involving all {\it set operators}) we choose a different approach
@@ -3039,7 +3039,7 @@ file {\tt $\ldots$/src/backend/parser/keywords.c}:
30393039
};
30403040
\end{verbatim}
30413041
%
3042-
<step> <productname>Postgres</productname> contains functions to convert the internal
3042+
<step> <productname>PostgreSQL</productname> contains functions to convert the internal
30433043
representation of a {\it parsetree} or {\it plantree} into an ASCII
30443044
representation (that can easily be printed to the screen (for
30453045
debugging purposes) or be stored in a file) and vice versa. These
@@ -3629,7 +3629,7 @@ troubles in the {\it transforming logic}.
36293629
\end{figure}
36303630
%
36313631
<step> Transform the new {\it operator tree} into DNF (disjunctive normal
3632-
form). <productname>Postgres</productname> does not provide any function for the transformation
3632+
form). <productname>PostgreSQL</productname> does not provide any function for the transformation
36333633
into DNF but it provides a function {\tt cnfify()} that performs a
36343634
transformation into CNF (conjunctive normal form). So we can easily
36353635
make use of this function when we exchange every {\tt OR} with an {\tt

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

Lines changed: 28 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -2,15 +2,15 @@
22
<TITLE>Architecture</TITLE>
33

44
<Sect1 id="arch-pg-concepts">
5-
<Title><ProductName>Postgres</ProductName> Architectural Concepts</Title>
5+
<Title><ProductName>PostgreSQL</ProductName> Architectural Concepts</Title>
66

77
<Para>
88
Before we begin, you should understand the basic
9-
<ProductName>Postgres</ProductName> system architecture. Understanding how the
10-
parts of <ProductName>Postgres</ProductName> interact will make the next chapter
9+
<ProductName>PostgreSQL</ProductName> system architecture. Understanding how the
10+
parts of <ProductName>PostgreSQL</ProductName> interact will make the next chapter
1111
somewhat clearer.
12-
In database jargon, <ProductName>Postgres</ProductName> uses a simple "process
13-
per-user" client/server model. A <ProductName>Postgres</ProductName> session
12+
In database jargon, <ProductName>PostgreSQL</ProductName> uses a simple "process
13+
per-user" client/server model. A <ProductName>PostgreSQL</ProductName> session
1414
consists of the following cooperating Unix processes (programs):
1515

1616
<ItemizedList>
@@ -80,19 +80,37 @@ From that point on, the frontend process and the backend
8080
</Para>
8181

8282
<Para>
83-
You should also be aware that the <Application>postmaster</Application> and
84-
postgres servers run with the user-id of the <ProductName>Postgres</ProductName>
83+
You should also be aware that the <Application>postmaster</Application> and
84+
postgres servers run with the user-id of the <ProductName>PostgreSQL</ProductName>
8585
<quote>superuser</>.
86-
Note that the <ProductName>Postgres</ProductName> superuser does not
86+
Note that the <ProductName>PostgreSQL</ProductName> superuser does not
8787
have to be any particular user (e.g., a user named
8888
<literal>postgres</literal>), although many systems are installed that way.
89-
Furthermore, the <ProductName>Postgres</ProductName> superuser should
89+
Furthermore, the <ProductName>PostgreSQL</ProductName> superuser should
9090
definitely not be the Unix superuser, <literal>root</literal>!
91-
It is safest if the <ProductName>Postgres</ProductName> superuser is an
91+
It is safest if the <ProductName>PostgreSQL</ProductName> superuser is an
9292
ordinary, unprivileged user so far as the surrounding Unix system is
9393
concerned.
9494
In any case, all files relating to a database should belong to
9595
this <ProductName>Postgres</ProductName> superuser.
9696
</Para>
9797
</sect1>
9898
</Chapter>
99+
100+
<!-- Keep this comment at the end of the file
101+
Local variables:
102+
mode:sgml
103+
sgml-omittag:nil
104+
sgml-shorttag:t
105+
sgml-minimize-attributes:nil
106+
sgml-always-quote-attributes:t
107+
sgml-indent-step:1
108+
sgml-indent-tabs-mode:nil
109+
sgml-indent-data:t
110+
sgml-parent-document:nil
111+
sgml-default-dtd-file:"./reference.ced"
112+
sgml-exposed-tags:nil
113+
sgml-local-catalogs:("/usr/share/sgml/catalog")
114+
sgml-local-ecat-files:nil
115+
End:
116+
-->

‎doc/src/sgml/array.sgml‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.15 2001/11/19 09:05:00 tgl Exp $ -->
1+
<!-- $Header: /cvsroot/pgsql/doc/src/sgml/array.sgml,v 1.16 2001/11/2105:53:40 thomas Exp $ -->
22

33
<chapter id="arrays">
44
<title>Arrays</title>
@@ -8,7 +8,7 @@
88
</indexterm>
99

1010
<para>
11-
<productname>Postgres</productname> allows columns of a table to be
11+
<productname>PostgreSQL</productname> allows columns of a table to be
1212
defined as variable-length multidimensional arrays. Arrays of any
1313
built-in type or user-defined type can be created. To illustrate
1414
their use, we create this table:
@@ -66,7 +66,7 @@ SELECT name FROM sal_emp WHERE pay_by_quarter[1] &lt;&gt; pay_by_quarter[2];
6666
</programlisting>
6767

6868
The array subscript numbers are written within square brackets.
69-
<productname>Postgres</productname> uses the
69+
<productname>PostgreSQL</productname> uses the
7070
<quote>one-based</quote> numbering convention for arrays, that is,
7171
an array of n elements starts with <literal>array[1]</literal> and
7272
ends with <literal>array[n]</literal>.

0 commit comments

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