Open Source RDBMS - Seamless, Scalable, Stable and Free

한국어 | Login |Register

Versions available for this page: CUBRID 8.4.3 | 

Other Parameters

The following are other parameters. The type and value range for each parameter are as follows:

Parameter Name

Type

Default Value

Min.

Max.

access_ip_control

bool

no

 

 

access_ip_control_file

string

 

 

 

auto_restart_server

bool

yes

 

 

index_scan_in_oid_order

bool

no

 

 

index_unfill_factor

float

0.05

0

0.5

java_stored_procedure

bool

no

 

 

multi_range_optimization_limit

int

100

0

10000

pthread_scope_process

bool

yes

 

 

server

string

 

 

 

service

string

 

 

 

session_state_timeout

int

21600 (6 hours)

60 (1 minute)

31536000 (1 year)

single_byte_compare

bool

no

 

 

sql_trace_slow_msec

int -1 0

86400000 (24hour)

sql_trace_execution_plan

bool no    

use_orderby_sort_limit

bool

yes

 

 

access_ip_control

access_ip_control is a parameter used to configure whether to use feature limiting the IP addresses that allow server access. The default value is no. For details, see Limiting Database Server Access.

access_ip_control_file

access_ip_control_file is a parameter used to configure the file name in which the list of IP addresses allowed by servers is stored. If access_ip_control value is set to yes, database server allows the list of IP addresses only stored in the file specified by this parameter. For details, see Limiting Database Server Access.

auto_restart_server

auto_restart_server is a parameter used to configure whether to restart the process when it stops due to fatal errors being occurred in database server process. If auto_restart_server value is set to yes, the server process automatically restarts when it has stopped due to errors; it does not restart in case it stops by following normal process (by using STOP command).

index_scan_in_oid_order

index_scan_in_oid_order is a parameter used to configure the result data to be retrieved in OID order after the index scan. If the parameter is set to no, which is the default value, results are retrieved in data order; if it is set to yes, they are retrieved in OID order.

index_unfill_factor

If there is no free space because index pages are full when the INSERT or UPDATE operation is executed after the first index is created, the split of index page nodes occurs. This substantially affects the performance by increasing the operation time. index_unfill_factor is a parameter used to configure the percent of free space defined for each index page node when an index is created. The index_unfill_factor value is applied only when an index is created for the first time. The percent of free space defined for the page is not maintained dynamically. Its value ranges between 0 and 0.5. The default value is 0.05.

If an index is created without any free space for the index page node (index_unfill_factor is set to 0), the split of index page nodes occurs every time an additional insertion is made. This may degrade the performance.

If the value of index_unfill_factor is large, a large amount of free space is available when an index is created. Therefore, better performance can be obtained because the split of index nodes does not occur for a relatively long period of time until the free space for the nodes is filled after the first index is created.

If this value is small, the amount of free space for the nodes is small when an index is created. Therefore, it is likely that the index nodes are spilt by INSERT or UPDATE because free space for the index nodes is filled in a short period of time.

java_stored_procedure

java_stored_procedure is a parameter used to configure whether to use Java stored procedures by running the Java Virtual Machine (JVM). If the parameter is set to no, which is the default value, JVM is not executed; if it is set to yes, JVM is executed so you can use Java stored procedures. Therefore, configure the parameter to yes if you plan to use Java stored procedures.

multi_range_optimization_limit

If the number of rows specified by the LIMIT clause in the query, which has multiple ranges (col IN (?, ?, …,?)) and is available to use an index, is within the number specified in the multi_range_optimization_limit parameter, the optimization for the way of index sorting will be performed. The default value is 100.

For example, if a value for this parameter is set to 50, LIMIT 10 means that it is within the value specified by this parameter, so that the values that meet the conditions will be sorted to produce the result. If LIMIT is 60, it means that it exceeds the parameter configuration value, so that it gets and sorts out all values that meet the conditions.

Depending on the setting value, the differences are made between collecting the result with on-the-fly sorting of the intermediate values and sorting the result values after collecting them, and the bigger value could make more unfavorable performance.

pthread_scope_process

pthread_scope_process is a parameter used to configure the contention scope of threads. It only applies to AIX systems. If the parameter is set to no, the contention scope becomes PTHREAD_SCOPE_SYSTEM; if it is set to yes, it becomes PTHREAD_SCOPE_PROCESS. The default value is yes.

server

server is a parameter used to register the name of database server process which will run automatically when CUBRID server starts.

service

service is a parameter used to configure process that starts automatically when the CUBRID service starts. There are four types of processes: server, broker, manager, and heartbeat. Three processes are usually registered as in service=server,broker,manager.

  • If the parameter is set to server, the database process specified by the @server parameter gets started.
  • If the parameter is set to broker, the broker process gets started.
  • If the parameter is set to manager, the manager process gets started.
  • If the parameter is set to heartbeat, the HA-related processes get started.
session_state_timeout

session_state_timeout is a parameter used to define how long the CUBRID session data will be kept. The session data will be deleted when the driver terminates the connection or the session time expires. The session time will expire after the specified time if a client terminates abnormally.

Custom variables defined by SET and PREPARE statements can be deleted by DROP/DEALLOCATE statements before session timeout.

The default value is 21600 seconds (6 hours).

single_byte_compare

single_byte_compare is a parameter used to configure whether to compare strings in single byte unit. If the parameter is set to no, which is the default value, strings are compared in two byte unit; if it is set to yes, they are compared in single byte unit. That is, you can retrieve/compare strings on data stored as UTF-8.

use_orderby_sort_limit

use_orderby_sort_limit is a parameter used to configure whether to keep the intermediate result of sorting and merging process in the statement including the ORDER BY … LIMIT row_count clause as many as row_count. If it is set to yes, you can decrease unnecessary comparing and merging processes because as many as intermediate results will be kept as the value of row_count. The default value is yes.

sql_trace_slow_msec

sql_trace_slow_msec is a parameter used to configure the execution time of a query which will be judged as a long time execution. The default value is -1 and the maximum value is 86400000 msec (24 hour). 이다. -1 means that the infinite time, so any queries will not be judged as a long duration query. For details, note the below sql_trace_execution_plan.

Note sql_trace_slow_msec parameter judges the excessive execution time with the server’s query execution duration., MAX_QUERY_TIMEOUT broker parameter has the similar role with sql_trace_slow_msec, but this judges the query execution time based on the broker.

sql_trace_execution_plan

sql_trace_execution_plan is a parameter used to configure if the query plan of the long-duration-execution query is written to the log or not. The default value is no.

If it is set to yes, a long-duration-execution SQL, a query plan and the output of cubrid statdump command  are written to the server error log file(located on CUBRID/log/server directory) and the broker application server log file(located on CUBRID/log/broker/sql_log directory).

If it is set to no, only a long-duration-execution SQL is written, and the output of cubrid statdump command  is shown only when you do that command.

But, on the server error log file, the related informations are written only when the value of error_log_level is NOTIFICATION.