| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Moe <mohamed5432154321(at)gmail(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: pg dump.. issue with when using crontab |
| Date: | 2010-01-26 17:14:06 |
| Message-ID: | 14962.1264526046@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Moe <mohamed5432154321(at)gmail(dot)com> writes:
> 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.
cron jobs typically run with a very minimal PATH. I'll bet pg_dump
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Moe | 2010-01-26 17:25:50 | Re: pg dump.. issue with when using crontab |
| Previous Message | Keresztury Balázs | 2010-01-26 17:09:43 | create role in a pl/pgsql trigger |