mirror of
https://github.com/EnterpriseDB/repmgr.git
synced 2026-03-22 22:56:29 +00:00
Add TODO, update history for 1.1.0 release
This commit is contained in:
4
HISTORY
4
HISTORY
@@ -27,3 +27,7 @@
|
||||
Add info messages for database and general work done (Greg)
|
||||
Map old verbose flag into a useful setting for the new logger (Greg)
|
||||
Document repmgrd startup restrictions and log info about them (Greg)
|
||||
|
||||
1.1.0 2011-03-09
|
||||
Make options -U, -R and -p not mandatory (Jaime)
|
||||
|
||||
|
||||
21
TODO
Normal file
21
TODO
Normal file
@@ -0,0 +1,21 @@
|
||||
Known issues in repmgr
|
||||
======================
|
||||
|
||||
* The check for whether ``wal_keep_segments`` is considered large enough
|
||||
does a string comparison rather than an integer one. It can give both
|
||||
false positive (setting is large enough but flagged as too small) and
|
||||
false negative (setting is too small but not noted as such) errors.
|
||||
|
||||
* When running repmgr against a remote machine, operations that start
|
||||
the database server using the ``pg_ctl`` command may accidentally
|
||||
terminate after their associated ssh session ends.
|
||||
|
||||
* After running repmgrd as a regular foreground application, hitting
|
||||
control-C causes the program to crash.
|
||||
|
||||
Planned feature improvements
|
||||
============================
|
||||
|
||||
* Before running ``pg_start_backup()``, a sanity check that there is a
|
||||
a working ssh connection to the destination would help find
|
||||
configuration errors before disturbing the database.
|
||||
Reference in New Issue
Block a user