|
11 | 11 | <surname>Momjian</surname> |
12 | 12 | </author> |
13 | 13 | </authorgroup> |
14 | | -<date>1998-06-01</date> |
| 14 | +<date>1998-06-09</date> |
15 | 15 | </docinfo> |
16 | 16 | --> |
17 | 17 |
|
|
42 | 42 | system. This is all performed without having to allocate a lock for |
43 | 43 | every row like traditional database systems. So, basically, we no |
44 | 44 | longer are restricted by simple table-level locking; |
45 | | -we have something better than row-level |
46 | | -locking. |
| 45 | +we have something better than row-level locking. |
| 46 | + </para> |
| 47 | + <para> |
| 48 | +Another big benefit of MVCC is that <application>pg_dump</application> |
| 49 | + can now generate consistent backups of live, active databases, without |
| 50 | +blocking active transactions. |
47 | 51 | </para> |
48 | 52 | </listitem> |
49 | 53 | </varlistentry> |
|
154 | 158 | <title>Migration to v6.5</title> |
155 | 159 |
|
156 | 160 | <para> |
157 | | - A dump/restore using <application>pg_dump</application> |
158 | | - or <application>pg_dumpall</application> |
| 161 | + A dump/restore using <application>pg_dump</application> |
159 | 162 | is required for those wishing to migrate data from any |
160 | 163 | previous release of <productname>Postgres</productname>. |
| 164 | + <application>pg_upgrade</application> can <emphasis>not</emphasis> |
| 165 | + be used to upgrade to this release because the on-disk structure |
| 166 | + of the tables has changed compared to previous releases. |
161 | 167 | </para> |
162 | 168 |
|
163 | 169 | <para> |
@@ -365,6 +371,7 @@ fix for large object memory leakage, fix for pg_dumping(Tom) |
365 | 371 | INET type now respects netmask for comparisons |
366 | 372 | Make VACUUM ANALYZE only use a readlock(Vadim) |
367 | 373 | Allow VIEWs on UNIONS(Jan) |
| 374 | +pg_dump now can generate consistent snapshots on active databases(Vadim) |
368 | 375 |
|
369 | 376 | Source Tree Changes |
370 | 377 | ------------------- |
|