By running Pg-dump like this, do we need to type in pwd for login manually?
Thanks
Sent from my BlackBerry device on the Rogers Wireless Network
From: Moe <mohamed5432154321@xxxxxxxxx>
Date: Tue, 26 Jan 2010 19:25:50 +0200
To: <pgsql-general@xxxxxxxxxxxxxx>
Subject: Re: [GENERAL] pg dump.. issue with when using crontab
Thank you both, that did the trick.
Sincerely / Moe
Sincerely / Moe
On Tue, Jan 26, 2010 at 7:14 PM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
Moe <mohamed5432154321@xxxxxxxxx> writes:cron jobs typically run with a very minimal PATH. I'll bet pg_dump
> I have a simple script file db :
> #!/bin/bash
> pg_dump -U postgres prodDB > /var/a/db/$(date "+%Y-%m-%d_%H:%M")-prodDB.dump
> Which works fine when executed manually ( ./db ).. I get a dump file which
> is around 1.9 MB
> I run this script from the crontab schedueler (crontab -e) :
> # m h dom mon dow command
> 33 04 * * * /var/a/scripts/db
> Which appears to executing the script file, but what I get is zero sized
> dump files.
isn't in it. Try putting the full path to pg_dump in the script.
Also consider sending its stderr someplace more useful than /dev/null,
so that you're not flying blind while debugging problems ...
regards, tom lane
