Re: pg dump.. issue with when using crontab
От | steeles@gmail.com |
---|---|
Тема | Re: pg dump.. issue with when using crontab |
Дата | |
Msg-id | 145398635-1264544939-cardhu_decombobulator_blackberry.rim.net-2061734401-@bda103.bisx.prod.on.blackberry обсуждение исходный текст |
Ответ на | Re: pg dump.. issue with when using crontab (Moe <mohamed5432154321@gmail.com>) |
Ответы |
Re: pg dump.. issue with when using crontab
|
Список | pgsql-general |
I am new to posgres.
By running Pg-dump like this, do we need to type in pwd for login manually?
Thanks
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@gmail.com>
Date: Tue, 26 Jan 2010 19:25:50 +0200
To: <pgsql-general@postgresql.org>
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@sss.pgh.pa.us> wrote:
Moe <mohamed5432154321@gmail.com> 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
В списке pgsql-general по дате отправления: