Re: pg dump.. issue with when using crontab - Mailing list pgsql-general

From Moe
Subject Re: pg dump.. issue with when using crontab
Date
Msg-id 861fed221001260925k64e6cd32k3276f86a21c5080e@mail.gmail.com
Whole thread Raw
In response to Re: pg dump.. issue with when using crontab  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg dump.. issue with when using crontab  (steeles@gmail.com)
List pgsql-general
Thank you both, that did the trick.

Sincerely / Moe

On Tue, Jan 26, 2010 at 7:14 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
Moe <mohamed5432154321@gmail.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

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg dump.. issue with when using crontab
Next
From: "Keresztury Balazs"
Date:
Subject: row level security best practice