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

Commit0f83eee

Browse files
author
Liudmila Mantrova
committed
Doc: sync with EE - productname fixes from A.Lakhin
1 parentabf3e54 commit0f83eee

File tree

4 files changed

+10
-9
lines changed

4 files changed

+10
-9
lines changed

‎doc/src/sgml/mchar.sgml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
MS-SQL behavoir concerning end-of-value whitespace.
2424
</para>
2525
<para>
26-
Differences fromPostgreSQL standard CHAR and VARCHAR are:
26+
Differences from&productname; standard CHAR and VARCHAR are:
2727
</para>
2828
<itemizedlist>
2929
<listitem>

‎doc/src/sgml/plantuner.sgml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -11,20 +11,21 @@
1111
Whether somebody think it's bad or not, but sometime it's very
1212
interesting to be able to control planner (provide hints, which tell
1313
optimizer to ignore its algorithm in part), which is currently
14-
impossible in PostgreSQL. Oracle, for example, has over 120 hints,
14+
impossible in &productname; (and PostgreSQL).
15+
Oracle, for example, has over 120 hints,
1516
and Microsoft SQL Server also supports hints.
1617
</para>
1718
<para>
1819
This first version of plantuner provides a possibility to hide
19-
specified indexes fromPostgreSQL planner, so it will not use them.
20+
specified indexes from&productname; planner, so it will not use them.
2021
</para>
2122
<para>
2223
There are many situations when developer want to temporarily disable
2324
specific index(es), without dropping them, or to instruct planner to
2425
use specific index.
2526
</para>
2627
<para>
27-
Next, for some workloadPostgreSQL could be too pessimistic for
28+
Next, for some workload&productname; could be too pessimistic for
2829
newly created tables and assumes much more rows in table than
2930
it actually has. If plantuner.fix_empty_table GUC variable is set
3031
to true then module will set to zero the number of pages/tuples of

‎doc/src/sgml/ref/waitlsn.sgml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
<!--
22
doc/src/sgml/ref/waitlsn.sgml
3-
PostgreSQL documentation
3+
&productname; documentation
44
-->
55

66
<refentry id="SQL-WAITLSN">
@@ -37,7 +37,7 @@ WAITLSN <replaceable class="PARAMETER">'LSN'</replaceable> [ , <replaceable clas
3737
<para>
3838
<command>WAITLSN</command> provides a simple
3939
interprocess <acronym>LSN</> wait mechanism for a backends on slave
40-
in master-slave replication scheme on <productname>PostgreSQL</productname> database.
40+
in master-slave replication scheme on <productname>&productname;</productname> database.
4141
</para>
4242
</refsect1>
4343

‎doc/src/sgml/rowtypes.sgml

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -260,7 +260,7 @@ INSERT INTO mytab (complex_col.r, complex_col.i) VALUES(1.1, 2.2);
260260
</para>
261261

262262
<para>
263-
In <productname>PostgreSQL</>, a reference to a table name (or alias)
263+
In <productname>&productname;</>, a reference to a table name (or alias)
264264
in a query is effectively a reference to the composite value of the
265265
table's current row. For example, if we had a table
266266
<structname>inventory_item</> as shown
@@ -306,7 +306,7 @@ SELECT c.* FROM inventory_item c;
306306
<programlisting>
307307
SELECT c.name, c.supplier_id, c.price FROM inventory_item c;
308308
</programlisting>
309-
<productname>PostgreSQL</> will apply this expansion behavior to
309+
<productname>&productname;</> will apply this expansion behavior to
310310
any composite-valued expression, although as shown <link
311311
linkend="rowtypes-accessing">above</link>, you need to write parentheses
312312
around the value that <literal>.*</> is applied to whenever it's not a
@@ -322,7 +322,7 @@ SELECT (myfunc(x)).a, (myfunc(x)).b, (myfunc(x)).c FROM some_table;
322322

323323
<tip>
324324
<para>
325-
<productname>PostgreSQL</> handles column expansion by
325+
<productname>&productname;</> handles column expansion by
326326
actually transforming the first form into the second. So, in this
327327
example, <function>myfunc()</> would get invoked three times per row
328328
with either syntax. If it's an expensive function you may wish to

0 commit comments

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