Chapter 30. Server Run-time Environment

Table of Contents

30.1. The enterprisedb User Account

30.2. Creating a Database Cluster

30.3. Starting the Database Server

30.3.1. Server Start-up Failures
30.3.2. Client Connection Problems

30.4. Run-time Configuration

30.4.1. File Locations
30.4.2. Connections and Authentication
30.4.3. Dynamic Tuning
30.4.4. Resource Consumption
30.4.5. Write Ahead Log
30.4.6. Query Planning
30.4.7. Error Reporting and Logging
30.4.8. EnterpriseDB Auditing Settings
30.4.9. Runtime Statistics
30.4.10. Automatic Vacuuming
30.4.11. Client Connection Defaults
30.4.12. Version and Platform Compatibility
30.4.13. Lock Management
30.4.14. Preset Options
30.4.15. Short Options

30.5. Managing Kernel Resources

30.5.1. Shared Memory and Semaphores
30.5.2. Resource Limits
30.5.3. Linux Memory Overcommit

30.6. Shutting Down the Server

30.7. Secure TCP/IP Connections with SSH Tunnels

This chapter discusses how to set up and run the database server and the interactions with the operating system.

30.1. The enterprisedb User Account

As with any other server daemon that is connected to outside world, it is advisable to run EnterpriseDB under a separate user account. This user account should only own the data that is managed by the server, and should not be shared with other daemons. (For example, using the user nobody is a bad idea.) It is not advisable to install executables owned by this user because compromised systems could then modify their own binaries.

To add a Unix user account to your system, look for a command useradd or adduser. The user name enterprisedb is often used but is by no means required.

Note: The installers shipping with EnterpriseDB automatically create this account on your behalf if it does not already exist.