1-10 of 10 found
Check "Source specification" for more details. --recovery-delay (-w) Delay when recovering wal segments (in seconds). This is primarily used to keep window of safety before DELETE * FROM main_table…
… wal segment exists, and is ready to be restored ( vide --recovery-delay option). Handles also situations where there is finish request (both immediate and smart).
Instead it sends a SIGINT to pid and introduces a short delay, with hopes that the signal will be received before the delay ends. You can use it to write cancellation tests. | | conn.
… fail, omnipitr-backup-slave will retry 3 times, with 5 minute delay between tries. In case of errors when writing to local destination - it is skipped, and error is logged.
… fail, omnipitr-backup-master will retry 3 times, with 5 minute delay between tries. In case of errors when writing to local destination - it is skipped, and error is logged.
A delay between retries is highly recommendend and the length of that delay should be determined by how long a refresh run of the given table usually takes.
… tool to purge various emaj history tables, based on a retention delay. Change the internal way to register log sequence states. This has no impact for users. Minor coding changes.
In practice, TCP timeouts can delay critical configuration changes to actually happen in the case where a former forwarding node failed and needs to be bypassed by subscribers.
Index & constraint creation can be delayed until after the data has been moved to speed up the migration. ``` CREATE TABLE public.new_regular_table ( col1 bigint not null GENERATED BY DEFAULT AS…