From: | Bastiaan Olij <bastiaan(at)basenlily(dot)me> |
---|---|
To: | Dinesh Kumar <dinesh(dot)kumar(at)enterprisedb(dot)com> |
Cc: | pgAdmin Support <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: pgAgent - adding parameters to runs |
Date: | 2013-12-11 02:26:06 |
Message-ID: | 52A7CD3E.3030509@basenlily.me |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Hi Dinesh,
On 10/12/13 5:26 PM, Dinesh Kumar wrote:
>
> Does it
> <http://manojadinesh.blogspot.in/2012/10/windows-pgdump-script.html>
> work for you. Make this script as a single job to the pgAgent.
We already use that approach but it would still require us to configure
a job for each database that calls the batch file with the database name
as a parameter (which is how we are doing things today).
As we regularly add new databases and remove ones we no longer need that
gives us a lot of overhead in maintaining the pgAgent jobs with a high
risk of typos sneaking in when we do so.
None of these jobs are scheduled, we have a nightly backup script that
backs up all databases with one script that detects which databases
exist. These jobs are for incidental backups such as ones we run on an
individual database before performing schema changes or certain
processes where we need to be able to go back to backup if things go wrong.
Cheers,
Bas
From | Date | Subject | |
---|---|---|---|
Next Message | Dinesh Kumar | 2013-12-12 17:31:04 | Re: pgAgent - adding parameters to runs |
Previous Message | Dinesh Kumar | 2013-12-10 10:49:11 | Re: pgAdmin 1.18.0 + slony-I 2.2.0 + PG 9.3 |