On 8/15/16 2:33 AM, Venkata B Nagothi wrote: > During the recovery process, It would be nice if PostgreSQL generates an > error by aborting the recovery process (instead of starting-up the > cluster) if the intended recovery target point is not reached and give > an option to DBA to resume the recovery process from where it exactly > stopped.
Thom wrote a patch [1] recently that gives warnings in this case. You might want to have a look at that first. > The issue here is, if by any chance, the required WALs are not available > or if there is any WAL missing or corrupted at the restore_command > location, then PostgreSQL recovers until the end of the last available > WAL and starts-up the cluster. You can use pause_at_recovery_target/recovery_target_action (depending on your version) to prevent promotion. That would work for your stated scenario but not for the scenario where replay starts (or the database reaches consistency) after the recovery target. [1] https://www.postgresql.org/message-id/flat/CAA-aLv4K2-9a%2BcvK75dkZkYD1etxpaH%2B9HC0vm9Ebw2up9Co2A%40mail.gmail.com#caa-alv4k2-9a+cvk75dkzkyd1etxpah+9hc0vm9ebw2up9c...@mail.gmail.com -- -David da...@pgmasters.net -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
