You can use the DSI queue save interval or the materialization queue save interval to reconfigure the save intervals for a logical replicate database.
A save interval for a connection specifies how long messages will be retained in a stable queue before they can be deleted. If you set up a warm standby application through the usual procedure, the default settings will work correctly.
You can use configure logical connection to configure the DSI queue save interval and the materialization queue save interval for the logical connection.
See Replication Server Reference Manual > Replication Server Commands > configure logical connection.
By default, the DSI queue save interval for the logical connection is set to 'strict' when you create a standby database.
This causes Replication Server to retain DSI queue messages until they are delivered to the standby database. If you must change the DSI queue save interval for the logical connection, use the configure logical connection command.
configure logical connection to LDS.logical_pubs2 set save_interval to '60'
configure logical connection to LDS.logical_pubs2 set save_interval to 'strict'
The materialization queue save interval for the logical connection is set to 'strict' by default when you create a subscription.
This causes Replication Server to retain materialization queue messages until they are delivered to the standby database. If you must change the materialization queue save interval for the logical connection, use the configure logical connection command.
configure logical connection to LDS.logical_pubs2 set materialization_save_interval to '60'
configure logical connection to LDS.logical_pubs2 set materialization_save_interval to 'strict'