..................................................................................343 x 25.1. Benefits of WAL......................................................................................... row does not immediately remove the old version of the row. This approach is necessary to gain the benefits of multiversion concurrency control (see 315 Chapter 21. Routine Database Maintenance Tasks Chapter is more complex to administer than either of the previous approaches, but it has some significant benefits: • We do not need a perfectly consistent backup as the starting point. Any internal inconsistency

.....................................................................................323 25.1. Benefits of WAL......................................................................................... row does not immediately remove the old version of the row. This approach is necessary to gain the benefits of multiversion concurrency control (see Chapter 12): the row version must not be deleted while is more complex to administer than either of the previous approaches, but it has some significant benefits: • We do not need a perfectly consistent backup as the starting point. Any internal inconsistency

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: 92 Data Definition • Query performance can be improved dramatically in certain situations, particularly by a bulk DELETE. • Seldom-used data can be migrated to cheaper and slower storage media. These benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at views can be used instead. Such methods offer flexibility but do not have some of the performance benefits of built-in declarative partitioning. 5.11.2. Declarative Partitioning PostgreSQL allows you to

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: • Query performance can be improved dramatically in certain situations, particularly when most by a bulk DELETE. • Seldom-used data can be migrated to cheaper and slower storage media. These benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at views can be used instead. Such methods offer flexibility but do not have some of the performance benefits of built-in declarative partitioning. 5.11.2. Declarative Partitioning PostgreSQL allows you to

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: • Query performance can be improved dramatically for certain kinds of queries. • Update performance ensuing VACUUM overhead. • Seldom-used data can be migrated to cheaper and slower storage media. The benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at row does not immediately remove the old version of the row. This approach is necessary to gain the benefits of multiversion concurrency control (see Chapter 12): the row version must not be deleted while

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: • Query performance can be improved dramatically for certain kinds of queries. • Update performance ensuing VACUUM overhead. • Seldom-used data can be migrated to cheaper and slower storage media. The benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at row does not immediately remove the old version of the row. This approach is necessary to gain the benefits of multiversion concurrency control (see Chapter 12): the row version must not be deleted while

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: • Query performance can be improved dramatically in certain situations, particularly when most by a bulk DELETE. • Seldom-used data can be migrated to cheaper and slower storage media. These benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at views can be used instead. Such methods offer flexibility but do not have some of the performance benefits of built-in declarative partitioning. 5.11.2. Declarative Partitioning PostgreSQL allows you to

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: • Query performance can be improved dramatically in certain situations, particularly when most by a bulk DELETE. • Seldom-used data can be migrated to cheaper and slower storage media. These benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at views can be used instead. Such methods offer flexibility but do not have some of the performance benefits of built-in declarative partitioning. 5.11.2. Declarative Partitioning PostgreSQL allows you to

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: 95 Data Definition • Query performance can be improved dramatically in certain situations, particularly by a bulk DELETE. • Seldom-used data can be migrated to cheaper and slower storage media. These benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at views can be used instead. Such methods offer flexibility but do not have some of the performance benefits of built-in declarative partitioning. 5.12.2. Declarative Partitioning PostgreSQL allows you to

what is logically one large table into smaller physical pieces. Partitioning can provide several benefits: • Query performance can be improved dramatically in certain situations, particularly when most by a bulk DELETE. • Seldom-used data can be migrated to cheaper and slower storage media. These benefits will normally be worthwhile only when a table would otherwise be very large. The exact point at views can be used instead. Such methods offer flexibility but do not have some of the performance benefits of built-in declarative partitioning. 5.12.2. Declarative Partitioning PostgreSQL allows you to