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 Symfoware Server.
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.
Direct editing of each configuration file is possible with a text editor.
See
Refer to "Server Configuration" and "Client Authentication" in "Server Administration" in the PostgreSQL Documentation for information on the parameters.
The postgresql.conf parameters that can be changed in WebAdmin are shown below:
Tab | WebAdmin item | Parameter |
|---|---|---|
Character Code | Character Set | client_encoding |
Message Locale | lc_messages | |
Communication | Port Number | port |
Max Connection | max_connections | |
SQL Options | Interpretation of Expression = NULL | transform_null_equals |
Date Output Format | DateStyle (*1) | |
Interval Oputput Format | IntervalStyle | |
The 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(Unit:KB) | work_mem |
Share Buffer(Unit:KB) | shared_buffers |
*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.
Parameters set by WebAdmin during instance startup are shown below (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_directory | '/var/tmp/symfo_version/instanceAdmin_instanceName/log' |
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) |
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 Symfoware Server, 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 L Configuring Kernel Parameters", and "Managing Kernel Resources" in "Server Administration" in the PostgreSQL Documentation for information on tuning kernel parameters.
Note
Do not directly edit the following postgresql.conf parameters with a text editor, otherwise WebAdmin may not work properly if you make a mistake):
port
archive_mode
archive_command
wal_level
log_line_prefix
log_destination
logging_collector
log_directory
log_file_mode
log_filename
log_truncate_on_rotation
log_rotation_age
backup_destination
You must take care with the following parameter:
superuser_reserved_connections
Set it to a number that includes the 3 connections required in WebAdmin (the default is 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.
If you specify an item or value that cannot be set by WebAdmin when editing the pg_hba.conf file with a text editor, it will not be possible to reference that line from WebAdmin.
