You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the docs section 20, "Starting and Stopping", pgbackrest is referred to as a "service".
I would argue that on Linux, the word "service" has quite a specific well-understood meaning, i.e. a daemon.
Meanwhile, my understanding of the docs, is that when you talk about "Stop the pgBackRest services" and "Start the pgBackRest services", what you are really doing is "Disable pgBackRest configuration" and "Enable pgBackRest configuration".
In and itself pgbackrest does nothing unless you manually run it or call it via cron or systemd timers. So it doesn't meet the definition of a "service" IMHO.
The text was updated successfully, but these errors were encountered:
Well, pgbackrest does also run as a service, but I see what you are getting at.
But I don't think Disable pgBackRest configuration really describes it either. Really what we are doing here is stopping writes to the repo going forward, but in fact stop will terminate any pgbackrest process that is currently running.
In truth I rather regret this feature. It was written for a particular user use case years ago and just didn't have enough thought put into it. Now it sort of works for certain use cases but I don't think it is effective overall.
In the docs section 20, "Starting and Stopping",
pgbackrest
is referred to as a "service".I would argue that on Linux, the word "service" has quite a specific well-understood meaning, i.e. a daemon.
Meanwhile, my understanding of the docs, is that when you talk about "Stop the pgBackRest services" and "Start the pgBackRest services", what you are really doing is "Disable pgBackRest configuration" and "Enable pgBackRest configuration".
In and itself
pgbackrest
does nothing unless you manually run it or call it via cron or systemd timers. So it doesn't meet the definition of a "service" IMHO.The text was updated successfully, but these errors were encountered: