Re: problema con pg_dum

From: toruvinn <toruvinn(at)lain(dot)pl>
To: Avilio Alarcón <aalarcon(at)grupoaventura(dot)com(dot)py>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: problema con pg_dum
Date: 2008-07-01 20:15:08
Message-ID: op.udmqjiyv33x80h@insanity.lain.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, 01 Jul 2008 19:44:28 +0200, Avilio Alarcón
<aalarcon(at)grupoaventura(dot)com(dot)py> wrote:
> pg_dump: not found
I have no idea what you just said, but I think I understand the problem.
Cron's PATH is reset to quite simple value in each cron script, so,
instead of:
> pg_dump -Ft -b radius > $(date +%Y%m%d)_aloradius_radius.tar
use
> /usr/bin/pg_dump -Ft -b radius > $(date +%Y%m%d)_aloradius_radius.tar
(or wherever your pg_dump is)
I'd also suggest using /bin/gzip instead of just gzip.

Regards,
--
ru

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Hiroshi Saito 2008-07-01 23:55:43 Re: BUG #4274: uuid returns duplicate values
Previous Message Avilio Alarcón 2008-07-01 17:44:28 problema con pg_dum