File tree 2 files changed +12
-8
lines changed
2 files changed +12
-8
lines changed Original file line number Diff line number Diff line change 2
2
PostgreSQL TODO List
3
3
====================
4
4
Current maintainer: Bruce Momjian (bruce@momjian.us)
5
- Last updated: Mon Apr 2 18:46:07 EDT 2007
5
+ Last updated: Mon Apr 2 18:48:47 EDT 2007
6
6
7
7
The most recent version of this document can be viewed at
8
8
http://www.postgresql.org/docs/faqs.TODO.html.
@@ -1169,9 +1169,11 @@ Vacuum
1169
1169
1170
1170
* Improve speed with indexes
1171
1171
1172
- For large table adjustments during VACUUM FULL, it is faster to
1173
- reindex rather than update the index. Also, index updates can
1174
- bloat the index.
1172
+ For large table adjustments during VACUUM FULL, it is faster to cluster
1173
+ or reindex rather than update the index. Also, index updates can bloat
1174
+ the index.
1175
+
1176
+ http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php
1175
1177
1176
1178
* Reduce lock time during VACUUM FULL by moving tuples with read lock,
1177
1179
then write lock and truncate table
Original file line number Diff line number Diff line change 8
8
< body bgcolor ="#FFFFFF " text ="#000000 " link ="#FF0000 " vlink ="#A00000 " alink ="#0000FF ">
9
9
< h1 > < a name ="section_1 "> PostgreSQL TODO List</ a > </ h1 >
10
10
< p > Current maintainer: Bruce Momjian (< a href ="mailto:bruce@momjian.us "> bruce@momjian.us</ a > )< br />
11
- Last updated: Mon Apr 2 18:46:07 EDT 2007
11
+ Last updated: Mon Apr 2 18:48:47 EDT 2007
12
12
</ p >
13
13
< p > The most recent version of this document can be viewed at< br />
14
14
< a href ="http://www.postgresql.org/docs/faqs.TODO.html "> http://www.postgresql.org/docs/faqs.TODO.html</ a > .
@@ -1037,9 +1037,11 @@ <h1><a name="section_15">Vacuum</a></h1>
1037
1037
1038
1038
< ul >
1039
1039
< li > Improve speed with indexes
1040
- < p > For large table adjustments during VACUUM FULL, it is faster to
1041
- reindex rather than update the index. Also, index updates can
1042
- bloat the index.
1040
+ < p > For large table adjustments during VACUUM FULL, it is faster to cluster
1041
+ or reindex rather than update the index. Also, index updates can bloat
1042
+ the index.
1043
+ </ p >
1044
+ < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php "> http://archives.postgresql.org/pgsql-hackers/2007-03/msg00024.php</ a >
1043
1045
</ p >
1044
1046
</ li > < li > Reduce lock time during VACUUM FULL by moving tuples with read lock,
1045
1047
then write lock and truncate table
You can’t perform that action at this time.
0 commit comments