 PostgreSQL 8.2 DocumentationIt may be safe to turn off this parameter if you have hardware (such as a battery-backed disk controller) 307 Chapter 17. Server Configuration or file-system software that reduces the risk of partial adjust how this is done.) Next, there may be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are passed be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has0 码力 | 1762 页 | 5.43 MB | 1 年前3 PostgreSQL 8.2 DocumentationIt may be safe to turn off this parameter if you have hardware (such as a battery-backed disk controller) 307 Chapter 17. Server Configuration or file-system software that reduces the risk of partial adjust how this is done.) Next, there may be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are passed be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has0 码力 | 1762 页 | 5.43 MB | 1 年前3
 PostgreSQL 9.0 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2561 页 | 5.55 MB | 1 年前3 PostgreSQL 9.0 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2561 页 | 5.55 MB | 1 年前3
 PostgreSQL 8.3 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are passed be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has write-back, and the same concerns about data loss exist for write-back drive caches as exist for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2143 页 | 4.58 MB | 1 年前3 PostgreSQL 8.3 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are passed be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has write-back, and the same concerns about data loss exist for write-back drive caches as exist for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2143 页 | 4.58 MB | 1 年前3
 PostgreSQL 8.3 DocumentationIt might be safe to turn off this parameter if you have hardware (such as a battery- backed disk controller) or file-system software that reduces the risk of partial page writes to an acceptably low level wal_sync_method parameter to adjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID con- troller cards. Some of these caches are write-through be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has0 码力 | 2015 页 | 4.54 MB | 1 年前3 PostgreSQL 8.3 DocumentationIt might be safe to turn off this parameter if you have hardware (such as a battery- backed disk controller) or file-system software that reduces the risk of partial page writes to an acceptably low level wal_sync_method parameter to adjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID con- troller cards. Some of these caches are write-through be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has0 码力 | 2015 页 | 4.54 MB | 1 年前3
 PostgreSQL 8.4 DocumentationIt might be safe to turn off this parameter if you have hardware (such as a battery- backed disk controller) or file-system software that reduces the risk of partial page writes to an acceptably low level wal_sync_method parameter to adjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID con- troller cards. Some of these caches are write-through be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has0 码力 | 2224 页 | 5.05 MB | 1 年前3 PostgreSQL 8.4 DocumentationIt might be safe to turn off this parameter if you have hardware (such as a battery- backed disk controller) or file-system software that reduces the risk of partial page writes to an acceptably low level wal_sync_method parameter to adjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID con- troller cards. Some of these caches are write-through be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has0 码力 | 2224 页 | 5.05 MB | 1 年前3
 PostgreSQL 8.4 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are passed be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has write-back, and the same concerns about data loss exist for write-back drive caches as exist for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2371 页 | 5.09 MB | 1 年前3 PostgreSQL 8.4 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are passed be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backed caches, meaning the card has write-back, and the same concerns about data loss exist for write-back drive caches as exist for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2371 页 | 5.09 MB | 1 年前3
 PostgreSQL 9.0 Documentationwal_sync_method parameter to adjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID con- troller cards. Some of these caches are write-through be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2401 页 | 5.50 MB | 1 年前3 PostgreSQL 9.0 Documentationwal_sync_method parameter to adjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID con- troller cards. Some of these caches are write-through be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer-grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2401 页 | 5.50 MB | 1 年前3
 PostgreSQL 9.1 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2836 页 | 6.62 MB | 1 年前3 PostgreSQL 9.1 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 2836 页 | 6.62 MB | 1 年前3
 PostgreSQL 9.2 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 3007 页 | 7.07 MB | 1 年前3 PostgreSQL 9.2 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 3007 页 | 7.07 MB | 1 年前3
 PostgreSQL 9.3 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 3183 页 | 7.53 MB | 1 年前3 PostgreSQL 9.3 Documentationadjust how this is done.) Next, there might be a cache in the disk drive controller; this is particularly common on RAID controller cards. Some of these caches are write-through, meaning writes are sent be a reliability hazard because the memory in the disk controller cache is volatile, and will lose its contents in a power failure. Better controller cards have battery-backup units (BBUs), meaning the card write-back, and the same concerns about data loss exist for write-back drive caches as for disk controller caches. Consumer- grade IDE and SATA drives are particularly likely to have write-back caches that0 码力 | 3183 页 | 7.53 MB | 1 年前3
共 38 条
- 1
- 2
- 3
- 4













