Types to numeric before dividing and back to money afterwards. (The latter is preferable to avoid risk- ing precision loss.) When a money value is divided by another money value, the result is double precision guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 389 III

guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 1. You can encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. 472 Chapter 17. Server Setup and Operation In order for

value to numeric before dividing and back to money afterwards. (The latter is preferable to avoid risk- ing precision loss.) When a money value is divided by another money value, the result is double precision guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 1. You can

guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 1. You can encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. In order for the tunnel setup to succeed you must be allowed

guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 2. You can encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. In order for the tunnel setup to succeed you must be allowed

guaranteed in case of a crash of the database software; only abrupt operating system stoppage creates a risk of data loss or corruption when these settings are used. • Place the database cluster’s data directory synchronous_commit; there might be no need to write the WAL to disk on every commit. This setting does risk transaction loss (though not data corruption) in case of a crash of the database alone. 381 III encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. In order for the tunnel setup to succeed you must be allowed

encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. In order for the tunnel setup to succeed you must be allowed evaluation. The default setting is two megabytes (2MB), which is conservatively small and unlikely to risk crashes. However, it might be too small to allow execution of complex functions. Only superusers can is three times wal_writer_delay.) Unlike fsync, setting this parameter to off does not create any risk of database inconsistency: an operating system or database crash might result in some recent allegedly-committed

encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. In order for the tunnel setup to succeed you must be allowed evaluation. The default setting is two megabytes (2MB), which is conserva- tively small and unlikely to risk crashes. However, it might be too small to allow execution of complex functions. Only superusers can is three times wal_writer_delay.) Unlike fsync, setting this parameter to off does not create any risk of database inconsistency: an operating system or database crash might result in some recent allegedly-committed

encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. In order for the tunnel setup to succeed you must be allowed evaluation. The default setting is two megabytes (2MB), which is conserva- tively small and unlikely to risk crashes. However, it might be too small to allow execution of complex functions. Only superusers can corruption might occur. (Crashes of the database software itself are not a risk factor here. Only an operating-system-level crash creates a risk of corruption.) Due to the risks involved, there is no universally

encrypted between the SSH server and the PostgreSQL server. This should not pose any extra security risk as long as they are on the same machine. 404 Chapter 17. Server Setup and Operation In order for evaluation. The default setting is two megabytes (2MB), which is conservatively small and unlikely to risk crashes. However, it might be too small to allow execution of complex functions. Only superusers can corruption might occur. (Crashes of the database software itself are not a risk factor here. Only an operating-system-level crash creates a risk of corruption.) Due to the risks involved, there is no universally