Hackers, Someone brought me an issue that recovery_target_time and standby_mode weren't working as they expected. I think that the way they work now makes sense, but we do need to clarify it in the docs. However, I'm posting this to hackers first in case the way these two work together *isn't* as intended.
Setup: two servers are restored from the same pgBarman archive. The master is brought to a specific point in time using recovery_target_time. Then they user attempts to do the same with the new replica. recovery.conf: recovery_target_time = 'SOME-PAST-TIMESTAMP' standby_mode = on primary_conninfo = 'host=mymaster user=postgres port=5432' How It Works Now: When the recovery_target_time is reached, standby_mode is ignored and the server comes up as a standalone. How The User Wanted It To Work: When the recovery_target_time is reached, switch to streaming replication and stay a standby. Note that there is a workaround for what the user wants to do. I'm just trying to clarify what our desired behavior is. From there we can either work on patches or on doc fixes. -- Josh Berkus PostgreSQL Experts Inc. http://pgexperts.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
