From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, hvjunk <hvjunk(at)gmail(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_start/stop_backup non-exclusive scripts to snapshot |
Date: | 2017-07-05 13:57:16 |
Message-ID: | CAB7nPqTKapELC9OLapfo+a8RhQB1SdqHv=TKUZ7xQsuzvXhQLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jul 5, 2017 at 10:47 PM, Melvin Davidson <melvin6925(at)gmail(dot)com> wrote:
> Your criticism is noted, however, I have used it many times in the past with absolutely no problem.
Plug off the server on which is stored the backup just after your
script finishes, you have a good chance to be surprised if you try to
restore from this backup later on.
> I submitted that script as a possible solution
> to the op's problem/question. If you have an alternate solution or can make improvements to it, then I am sure the op and I would welcome them.
Stephen has mentioned two of them, with hundreds of man hours spent in
developing those backup tools to be robust solutions, done by
specialists on the matter.
--
Michael
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2017-07-05 14:02:19 | Re: Imperative Query Languages |
Previous Message | Bill Moran | 2017-07-05 13:51:38 | Re: Strange case of database bloat |