Setting Parameter Values
The parameters documented on this page apply to users of Spock extension version 4.0 and higher. You can use the pgEdge Platform UM module to upgrade your installed version of the Spock extension.
pgEdge Platform uses parameter settings in the postgresql.conf (opens in a new tab) file to manage the replication behavior of PostgreSQL and the extensions that provide advanced functionality for pgEdge.
The parameters are set to their default values when you install pgEdge. You can modify the parameter values later, but should consider the default values to be the minimum values required; we do not recommend lowering these values:
| Functionality | Parameter Name | Default Setting and Description |
|---|---|---|
| Replication | hot_standby_feedback (opens in a new tab) | on |
| Replication | max_worker_processes (opens in a new tab) | 12 |
| Replication | max_replication_slots (opens in a new tab) | 16 |
| Replication | max_wal_senders (opens in a new tab) | 16 |
| Replication | shared_preload_libraries (opens in a new tab) | pg_stat_statements, snowflake, spock |
| Auto-DDL | spock.allow_ddl_from_functions (opens in a new tab) | on |
| Spock | spock.conflict_resolution | last_update_wins |
| Spock | spock.conflict_log_level | The log level to use for logging conflicts; the default is: DEBUG. |
| Auto-DDL | spock.enable_ddl_replication (opens in a new tab) | on |
| ACE | [spock.exception_behavior] | discard or transdiscard; the default is transdiscard. If an error occurs, all operations are rolled back (transdiscard) and operations are recorded in spock.exception_log, regardless of succeeding or failing. |
| ACE | [spock.exception_logging] | none,discard, or all Use spock.exception_logging to specify a preference about logging exceptions when they occur. |
| Auto-DDL | spock.include_ddl_repset (opens in a new tab) | on |
| Spock | spock.readonly (opens in a new tab) | all, user, or off. The default of off means that the database is fully read/write. user means database can be updated by replication, but not by a client application. all means database is 100% read only and not even spock can modify it. Read only workloads are always allowed. |
| Spock | spock.save_resolutions (opens in a new tab) | on |
| Snowflake | snowflake.node (opens in a new tab) | The snowflake node number; this is unique to each node. |
| Replication | track_commit_timestamp (opens in a new tab) | on |
| Replication | wal_level (opens in a new tab) | logical |
| Replication | wal_sender_timeout (opens in a new tab) | 5s |
Note: On a Multi-master replication system, these parameter settings should be identical on each node. Additionally, the roles created on each node should be the same.