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

Commit53a04e0

Browse files
committed
Release note updates.
1 parenta5e1ccc commit53a04e0

File tree

1 file changed

+109
-123
lines changed

1 file changed

+109
-123
lines changed

‎doc/src/sgml/release.sgml

Lines changed: 109 additions & 123 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
<!--
2-
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian Exp $
2+
$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.343 2005/08/23 12:46:35 momjian Exp $
33
-->
44

55
<appendix id="release">
@@ -23,11 +23,11 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
2323
<variablelist>
2424

2525
<varlistentry>
26-
<term>
26+
<term>
2727
Improve concurrent access to the shared buffer cache (Tom)
28-
</term>
28+
</term>
2929

30-
<listitem>
30+
<listitem>
3131
<para>
3232
This was accomplished by eliminating global locks and using a clock
3333
sweep algorithm to find free buffers.
@@ -37,59 +37,87 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
3737

3838
<varlistentry>
3939
<term>
40-
Allow indexes to be used for MIN/MAX (Tom)
40+
Allow indexes to be used for MIN/MAX (Tom)
4141
</term>
4242

4343
<listitem>
44-
<para>
44+
<para>
4545
In previous releases, the only way to use index for MIN/MAX was to rewrite
46-
the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens
46+
the query as SELECT col FROM tab ORDER BY col LIMIT 1. This now happens
4747
automatically.
48-
</para>
48+
</para>
4949
</listitem>
5050
</varlistentry>
5151

5252
<varlistentry>
5353
<term>
54-
Add in-memory bitmaps which allows multiple indexes to be merged in a
55-
single query (Tom)
56-
</term>
54+
Add in-memory bitmaps which allows multiple indexes to be merged in a
55+
single query (Tom)
56+
</term>
5757

58-
<listitem>
58+
<listitem>
5959
<para>
6060
This allows multiple indexes to be combined to access a single
6161
table.
62-
</para>
62+
</para>
6363
</listitem>
6464
</varlistentry>
6565

6666
<varlistentry>
6767
<term>
68-
</term>
68+
Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
69+
</term>
70+
71+
<listitem>
72+
<para>
73+
Two-phase commit allows transactions to be "prepared" on several
74+
computers, and once all computers have successfully prepared their
75+
transactions (and can not be rolled back) all transactions can be
76+
committed. Even if a machine crashes after a prepare, the prepared
77+
transaction can be committed after it is restarted. New syntax
78+
includes PREPARE TRANSACTION and COMMIT/ROLLBACK PREPARED. A new
79+
system view pg_prepared_xacts has also been added.
80+
</para>
81+
</listitem>
82+
</varlistentry>
6983

70-
<listitem>
84+
<varlistentry>
85+
<term>
86+
Replace pg_shadow and pg_group by new role-capable catalogs pg_authid
87+
and pg_auth_members.
88+
</term>
89+
90+
<listitem>
7191
<para>
72-
</para>
92+
Add SET ROLE (Stephen Frost)
93+
</para>
7394
</listitem>
7495
</varlistentry>
7596

7697
<varlistentry>
7798
<term>
78-
</term>
99+
Move /contrib/pgautovacuum into the main server (Alvaro Herrera)
100+
</term>
79101

80-
<listitem>
102+
<listitem>
81103
<para>
82-
</para>
104+
Add SET ROLE (Stephen Frost)
105+
</para>
83106
</listitem>
84107
</varlistentry>
85108

86109
<varlistentry>
87110
<term>
88-
</term>
111+
Add shared row level locks using SELECT ... FOR SHARE (Alvaro)
112+
</term>
89113

90-
<listitem>
114+
<listitem>
91115
<para>
92-
</para>
116+
While PostgreSQL's MVCC locking allows SELECT to never be blocked by writers
117+
and therefore does not need shared row locks for typical operations,
118+
shared locks are useful for applications that require shared row locking,
119+
and to reduce the locking requirements to maintain referential integrity.
120+
</para>
93121
</listitem>
94122
</varlistentry>
95123

@@ -154,6 +182,50 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
154182
</para>
155183
</listitem>
156184

185+
<listitem>
186+
<para>
187+
Add E'' syntax so eventually normal strings can treat backslashes
188+
literally (Bruce)
189+
</para>
190+
<para>
191+
Currently PostgreSQL considers a backslash to be a special character
192+
so the character after the backslash is treated specially. While this
193+
allows easy entry of special values, it is non-standard and makes
194+
porting of application from other databases more difficult. For this
195+
reason, the PostgreSQL project is moving to remove the special meaning
196+
of backslashes in strings, and allow only an E preceeding a string to
197+
turn on the special handling of backslashes. For this reason, this
198+
release adds several new GUC variables related to backslash
199+
processing:
200+
201+
escape_string_warning - warn about backslashes in non-E strings
202+
escape_string_syntax - does this release support the E'' syntax?
203+
standard_conforming_strings - does this release treat backslashes
204+
literally in non-E strings
205+
</para>
206+
<para>
207+
The last two values are read-only and should assist in the porting of
208+
applications. Applications can retrieve these values to know how
209+
backslashes are processed. In a later release,
210+
standard_conforming_strings will be true, meaning backslashes will be
211+
treated literally in non-E strings. To prepare for this change, use
212+
E'' strings in places that need special backslash processing, and turn
213+
on escape_string_warning to find additional strings that need to be
214+
converted to use E''.
215+
</para>
216+
</listitem>
217+
218+
<listitem>
219+
<para>
220+
Make REINDEX DATABASE reindex all indexes in the database (Tom)
221+
</para>
222+
<para>
223+
The old behavior of REINDEX database reindexed only system tables.
224+
This new behavior seems more intuitive. A new command REINDEX SYSTEM
225+
allows for reindexing just the system tables.
226+
</para>
227+
</listitem>
228+
157229
<listitem>
158230
<para>
159231
In psql, treat unquoted \{digit}+ sequences as octal (Bruce)
@@ -325,6 +397,13 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
325397
</para>
326398
</listitem>
327399

400+
<listitem>
401+
<para>
402+
Fix problem of OID wraparound conflicting with existing system objects
403+
(Tom)
404+
</para>
405+
</listitem>
406+
328407
<listitem>
329408
<para>
330409
Add warning about the need to increase "max_fsm_relations" and
@@ -360,7 +439,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
360439
<listitem>
361440
<para>
362441
Allow Kerberos name and user name case sensitivity to be specified from
363-
postgresql.conf
442+
postgresql.conf (Magnus)
364443
</para>
365444
</listitem>
366445

@@ -401,25 +480,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
401480
</para>
402481
</listitem>
403482

404-
<listitem>
405-
<para>
406-
Replace pg_shadow and pg_group by new role-capable catalogs pg_authid
407-
and pg_auth_members.
408-
</para>
409-
</listitem>
410-
411-
<listitem>
412-
<para>
413-
Add SET ROLE (Stephen Frost)
414-
</para>
415-
</listitem>
416-
417-
<listitem>
418-
<para>
419-
Move /contrib/pgautovacuum into the main server (Alvaro Herrera)
420-
</para>
421-
</listitem>
422-
423483
<listitem>
424484
<para>
425485
Add GUC variables to control keep-alive times for idle, interval, and
@@ -433,13 +493,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
433493
</para>
434494
</listitem>
435495

436-
<listitem>
437-
<para>
438-
Fix problem of OID wraparound conflicting with existing system objects
439-
(Tom)
440-
</para>
441-
</listitem>
442-
443496
</itemizedlist>
444497
</sect3>
445498

@@ -478,18 +531,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
478531
</para>
479532
</listitem>
480533

481-
<listitem>
482-
<para>
483-
Add shared row level locks using SELECT ... FOR SHARE (Alvaro)
484-
</para>
485-
<para>
486-
While PostgreSQL's MVCC locking allows SELECT to never be blocked by writers
487-
and therefore does not need shared row locks for typical operations,
488-
shared locks are useful for applications that require shared row locking,
489-
and to reduce the locking requirements to maintain referential integrity.
490-
</para>
491-
</listitem>
492-
493534
<listitem>
494535
<para>
495536
Add BETWEEN SYMMETRIC query syntax (Pavel Stehule)
@@ -502,39 +543,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
502543
</para>
503544
</listitem>
504545

505-
<listitem>
506-
<para>
507-
Add E'' syntax so eventually normal strings can treat backslashes
508-
literally (Bruce)
509-
</para>
510-
<para>
511-
Currently PostgreSQL considers a backslash to be a special character
512-
so the character after the backslash is treated specially. While this
513-
allows easy entry of special values, it is non-standard and makes
514-
porting of application from other databases more difficult. For this
515-
reason, the PostgreSQL project is moving to remove the special meaning
516-
of backslashes in strings, and allow only an E preceeding a string to
517-
turn on the special handling of backslashes. For this reason, this
518-
release adds several new GUC variables related to backslash
519-
processing:
520-
521-
escape_string_warning - warn about backslashes in non-E strings
522-
escape_string_syntax - does this release support the E'' syntax?
523-
standard_conforming_strings - does this release treat backslashes
524-
literally in non-E strings
525-
</para>
526-
<para>
527-
The last two values are read-only and should assist in the porting of
528-
applications. Applications can retrieve these values to know how
529-
backslashes are processed. In a later release,
530-
standard_conforming_strings will be true, meaning backslashes will be
531-
treated literally in non-E strings. To prepare for this change, use
532-
E'' strings in places that need special backslash processing, and turn
533-
on escape_string_warning to find additional strings that need to be
534-
converted to use E''.
535-
</para>
536-
</listitem>
537-
538546
<listitem>
539547
<para>
540548
Add NOWAIT option to SELECT ... FOR UPDATE/SHARE (Hans-Juergen Schoenig)
@@ -675,22 +683,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
675683

676684
<listitem>
677685
<para>
678-
Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
679-
680-
Two-phase commit allows transactions to be "prepared" on several
681-
computers, and once all computers have successfully prepared their
682-
transactions (and can not be rolled back) all transactions can be
683-
committed. Even if a machine crashes after a prepare, the prepared
684-
transaction can be committed after it is restarted. New syntax
685-
includes PREPARE TRANSACTION and COMMIT/ROLLBACK PREPARED. A new
686-
system view pg_prepared_xacts has also been added.
687-
</para>
688-
</listitem>
689-
690-
<listitem>
691-
<para>
692-
Have initdb create new standard database called "postgres" and convert utilities
693-
to use "postgres" rather than "template1" for standard lookups (Dave)
686+
Have initdb create new standard database called "postgres" and
687+
convert utilities to use "postgres" rather than "template1" for
688+
standard lookups (Dave)
694689
</para>
695690
<para>
696691
In prior releases, template1 was used both as a default
@@ -703,17 +698,6 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
703698
</para>
704699
</listitem>
705700

706-
<listitem>
707-
<para>
708-
Make REINDEX DATABASE reindex all indexes in the database (Tom)
709-
</para>
710-
<para>
711-
The old behavior of REINDEX database reindexed only system tables.
712-
This new behavior seems more intuitive. A new command REINDEX SYSTEM
713-
allows for reindexing just the system tables.
714-
</para>
715-
</listitem>
716-
717701
<listitem>
718702
<para>
719703
Create new reindexdb command-line utility by moving /contrib/reindexdb
@@ -960,7 +944,9 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
960944
<listitem>
961945
<para>
962946
Change pg_stat_* views to show TOAST tables (Tom)
963-
947+
</para>
948+
</listitem>
949+
964950
</itemizedlist>
965951
</sect3>
966952

@@ -1388,7 +1374,7 @@ $PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.342 2005/08/23 12:14:33 momjian
13881374

13891375
<listitem>
13901376
<para>
1391-
Streamline the passing information within the server, the optimizer,
1377+
Streamline the passingofinformation within the server, the optimizer,
13921378
and the lock system (Tom)
13931379
</para>
13941380
</listitem>

0 commit comments

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