... | @@ -117,3 +117,7 @@ Each server connected to the database is configured with a set of address pools. |
... | @@ -117,3 +117,7 @@ Each server connected to the database is configured with a set of address pools. |
|
*Note: skipping the existing entry upon insert can be achieved by using ON CONFLICT/DO NOTHING construct in PostgreSQL.*
|
|
*Note: skipping the existing entry upon insert can be achieved by using ON CONFLICT/DO NOTHING construct in PostgreSQL.*
|
|
|
|
|
|
When the server terminates it must not delete any entries from the `leaseX_avail` tables because another server may be using them. The may obviously lead to a dirty database including extraneous data for the leases which belong to the address pools not configured on any server. If this is a concern, it is possible to introduce a configuration parameter which enables cleanup of the stale entries. The cleanup may only be enabled in deployments where a single server is connected to the database at a given time.
|
|
When the server terminates it must not delete any entries from the `leaseX_avail` tables because another server may be using them. The may obviously lead to a dirty database including extraneous data for the leases which belong to the address pools not configured on any server. If this is a concern, it is possible to introduce a configuration parameter which enables cleanup of the stale entries. The cleanup may only be enabled in deployments where a single server is connected to the database at a given time.
|
|
|
|
|
|
|
|
# Implementation Tasks
|
|
|
|
|
|
|
|
TBD |
|
|
|
\ No newline at end of file |