WebAdmin operates and manages databases according to the contents of the following configuration files:
Contains various items of information that define the operating environment of Fujitsu Enterprise Postgres.
Contains various items of information related to client authentication.
These configuration files are deployed to a data storage destination. Data is written to them when the instance is created by WebAdmin and when settings are changed, and data is read from them when the instance is started and when information from the [Setting] menu is displayed.
See
Refer to "Server Configuration" and "Client Authentication" in "Server Administration" in the PostgreSQL Documentation for information on the parameters.
Note
WebAdmin checks for port number and backup storage path anomalies when various operations are performed. An anomaly occurs when the value of [Port number] and/or [Backup storage path] in WebAdmin is different from the value of the corresponding parameter in postgresql.conf. Refer to "Anomaly Detection and Resolution" in the Operation Guide for details.
The postgresql.conf parameters that can be changed in WebAdmin are shown below:
Section | WebAdmin item | postgresql.conf file parameter |
---|---|---|
Instance Configuration | ||
Character encoding | Character set | client_encoding |
Message locale | lc_messages | |
Communication | Max connections | max_connections |
SQL options | Transform NULL format | transform_null_equals |
Date output format | DateStyle (*1) | |
Interval output format | IntervalStyle | |
Number of digits for floating values | extra_float_digits | |
Transaction isolation levels | default_transaction_isolation | |
Currency format | lc_monetary | |
Date and time format | lc_time | |
Numerical value format | lc_numeric | |
Memory | Sort memory (KB) | work_mem |
Shared buffers (KB) | shared_buffers | |
Streaming replication | WAL level | wal_level |
Maximum WAL senders | max_wal_senders | |
WAL save size (MB) | wal_keep_size | |
Hot standby | hot_standby | |
Synchronous standby names | synchronous_standby_names | |
WAL receiver timeout (ms) | wal_receiver_timeout | |
Edit instance | ||
Instance name | n/a | |
Instance port | port | |
Backup storage path | backup_destination |
*1: If you specify "Postgres" as the output format, dates will be output in the "12-17-1997" format, not the "Wed Dec 17 1997" format used in the PostgreSQL Documentation.
Information
Calculate the maximum number of connections using the formula below:
maximumNumberOfConnections = maximumNumberOfConnectionsFromApplications + 3 (*1)
*1: 3 is the default number of connections required by the system.
Calculate the maximum number of connections using the following formula when changing superuser_reserved_connections (connections reserved for use by the superuser) in postgresql.conf.
maximumNumberOfConnections = maximumNumberOfConnectionsFromApplications + superuser_reserved_connections
Also check if the memory used exceeds the memory installed (refer to "Parameters automatically set by WebAdmin according to the amount of memory").
When modifying "Shared buffers" or "Max connections", edit the kernel parameter. Refer to "Appendix H Configuring Kernel Parameters", and "Managing Kernel Resources" in "Server Administration" in the PostgreSQL Documentation for details.
The following postgresql.conf parameters are set by WebAdmin during instance startup (they will be ignored even if specified in postgresql.conf):
Parameter | Value |
---|---|
listen_addresses | * |
log_destination | 'stderr,syslog' |
logging_collector | on |
log_line_prefix | '%e: %t [%p]: [%l-1] user = %u,db = %d,remote = %r app = %a ' |
log_filename (*1) (*2) | 'logfile-%a.log' |
log_file_mode | 0600 |
log_truncate_on_rotation | on |
log_rotation_age | 1d |
*1: The server logs are split into files based on the day of the week, and are rotated after each week.
*2: If the date changes while the instance is stopped, old logs are not deleted and continue to exist.
Manually delete old logs that are no longer required to release disk space.
The postgresql.conf parameters automatically set according to the amount of installed memory, during the creation of instances by WebAdmin, are shown below:
Parameter | Value |
---|---|
shared_buffers | 30% of the machine's installed memory |
work_mem | 30% of the machine's installed memory / max_connections / 2 |
effective_cache_size | 75% of the machine's installed memory |
maintenance_work_mem | 10% of the machine's installed memory / (1 + autovacuum_max_workers) (*1) |
*1: The value will be capped at 2097151 KB.
When determining the values to be configured in the above parameters, you must take into account any anticipated increases in access volume or effects on performance during business operations, such as the number of applications and commands that will access the instance, and the content of processes. Also, note that in addition to Fujitsu Enterprise Postgres, other software may be running on the actual database server. You will need to determine the degree of priority for the database and other software, as well as the memory allocation size.
WebAdmin automatically configures complex parameter settings such as those mentioned above, based on the size of the internal memory of the machine. This enables maximum leverage of the machine memory to facilitate resistance against fluctuations during business operations.
Accordingly, the effects of the above-mentioned factors must be estimated and taken into account when determining and configuring parameter values, so that memory resources can be effectively allocated among other software or instances, and so that adverse effects can be mutually avoided. Refer to "Memory" in "Resource Consumption", and "Planner Cost Constants" in "Query Planning", under "Server Administration" in the PostgreSQL Documentation for information on parameter values and required considerations.
Parameter values can be modified using the WebAdmin [Setting] menu, or edited directly using a text editor.
If adding an instance, determine the parameter values, including for existing instances, and make changes accordingly.
See
Kernel parameters need to be tuned according to the parameters being changed. Refer to "Appendix H Configuring Kernel Parameters", and "Managing Kernel Resources" in "Server Administration" in the PostgreSQL Documentation for information on tuning kernel parameters.
Note
You can edit postgresql.conf directly with a text editor. However, do not edit the following parameters. If you edit incorrectly, WebAdmin will not work correctly.
archive_mode
archive_command (Only allow changing compression settings)
wal_level
log_line_prefix
log_destination
logging_collector
log_directory
log_file_mode
log_filename
log_truncate_on_rotation
log_rotation_age
If you edit postgresql.conf directly, the records should be single line. WebAdmin will not work correctly if the record spans multiple lines.
If you change superuser_reserved_connections, set the value you want to change plus the number of connections required by WebAdmin of 3.
pg_hba.conf
Refer to "Client Authentication" in "Server Administration" in the PostgreSQL Documentation for information on content that can be configured in pg_hba.conf.
Note
Configure the instance administrator permissions in the "local" connection format settings. WebAdmin may not work properly if permissions are not configured.
You can also edit pg_hba.conf directly. However, do not modify items that cannot be configured in WebAdmin. WebAdmin does not work correctly.
If you edit pg_hba.conf directly, the records should be single line. WebAdmin will not work correctly if the record spans multiple lines.