lightdb_enable_default_tablespace (integer)
Enables or disables default tablespace lt_users for create database. This is off by default.
lightdb_external_virtual_ip (string)
Configure the external virtual IP. If there is an external virtual IP, before the standby automatically switches to primary, it will determine whether the local machine has this IP address. If there is no IP address, it will not be promoted automatically. see ltcluster
lightdb_auto_incre_null_mysql_compatible (integer)
this guc parameter controls whether or not compatible below mysql behavior. When mysql's table column is auto_increment and has not null constraint, it allow explicit insert null value to this column, and will use auto generated value as the value, in oracle and postgresql, it will error with non-violated not null. when this guc set on, and in mysql mode, it will compatible with mysql and success, else failed. the default value is off to comptible with previous version.
lt_statement_rollback_enable (integer)
Turn statement level rollback on or off in the transaction block. This is off by default. This function takes effect in Oracle or MySQL mode. Statement level rollback is enabled, and the performance loss is about 5%. It is better not to set this switch in the transaction block, which may cause unexpected errors.
lightdb_aborted_rollback (boolean)
Lightdb_aborted_rollback is off by default. Enable lightdb_aborted_rollback, report an error and rollback all statements when an error occurs in a transaction. The lt_statement_rollback_enable parameter has been opened, you cannot set Lightdb_aborted_rollback, it will fail to execute. The opposite is the same.
lightdb_sql_mode (String)
lightdb_sql_mode specifies some SQL execution rules, separated by commas. The following rules are supported: no_zero_date, uppercase_identifier.
This setting can be changed within individual sessions. But the rule of 'uppercase_identifier' is not suggested that. It should be enabled in the lightdb.conf as far as possible and don't modify it casually. For more information about the rule 'uppercase_identifier' could be found in create_table.sgml's section of 'column_name' and select.sgml's section of 'SELECT List' with some examples listed in 'Examples' as a guidance for how to use it.
lightdb_oracle_sql_mode (String)
lightdb_oracle_sql_mode is a user setting parameter on session. Set lightdb_oracle_sql_mode to 'show_identifier_uppercase' to display column name in uppercase by default when executed a select statement. More information about this function could be found in create_table.sgml's section of 'column_name' and select.sgml's section of 'SELECT List' with some examples listed in 'Examples' as a guidance for how to use it.
Set lightdb_oracle_sql_mode to 'selectfrom_tablename_uppercase' to support querying tables created using double quotes by using table names without double quotes. oracle selectfrom tablename uppercase show the example.
lightdb_cursor_after_commit (String)
Add GUC parameter lightdb_cursor_after_commit, When the parameter value is on, the cursor can continue after the transaction commits. When the parameter value is off, the cursor cannot proceed after the transaction is committed. The default value of this parameter is off.
lightdb_gtt_max_num (integer)
The maximum number of global temporary tables that can be used.
Multiple sessions using the same global temporary table counts as 1.
Specifically refers to the maximum number of sessions that can use different global temporary tables.
The default value of this parameter is 1000.
lightdb_result_cache_clean_interval (integer)
Result cache clean interval, the unit is seconds. Default is 0, means disable.
lightdb_enable_linear_parallel_worker_count (boolean)
This parameter force planner to compute parallel worker's num by linear algorithm. The threshold is 3 times the value of min_parallel_table_scan_size or min_parallel_index_scan_size.
lightdb_oracle_support_args_name_reference (boolean)
This parameter affects how stored procedures and functions in PACKAGE reference TYPE in Oracle mode, and the default value is "off". When enabled, it uses weak dependencies, allowing functions and stored procedures in the PACKAGE to reference TYPEs that have not yet been created. When disabled, it enforces strong dependencies, and in the case mentioned above, an error will be reported during CREATE PACKAGE, indicating that the TYPE does not exist.
It is not recommended to modify this parameter unless in special circumstances.
lightdb_oracle_enable_drop_package_body_equal_drop_package (boolean)
This parameter affects the behavior of DROP PACKAGE BODY in Oracle mode, and the default value is "on". When enabled, DROP PACKAGE BODY will also drop the PACKAGE along with it; when disabled, only the PACKAGE BODY will be dropped.
lightdb_cache_dostmt_plan (boolean)
This parameter force planner to cache dostmt plan if feasible. Default is on.