| From: | Chris Miles <chris_pg002(at)psychofx(dot)com> |
|---|---|
| To: | Jesse Burkhardt <jesse(at)skybuilders(dot)com> |
| Cc: | "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Automated backup problems - pg_dump |
| Date: | 2003-08-26 18:24:18 |
| Message-ID: | 3F4BA5D2.8010805@psychofx.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Yes the variable is actually: PGPASSWORD
I have a crond pg_dump script (as root) that sets this variable and
dumps with "-U postgres" and uses the variable successfully.
(7.2.4).
Cheers
CM
Stephan Szabo wrote:
> On Sun, 24 Aug 2003, Jesse Burkhardt wrote:
>>I am sure many of you have encountered the problems I am experiencing
>>with automating the pg_dump command from a cron. The problem arises from
>>a failure of this command to use the environmental variable,
>>PG_PASSWORD. (PGUSER, on the other hand, is picked up during command
>
> I think the environment variable is PGPASSWORD (no underscore) in at least
> 7.3 and above. Also, it's somewhat depricated in favor of using the
> .pgpass file.
--
Chris Miles
http://chrismiles.info/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rhaoni Chiu Pereira | 2003-08-26 19:11:56 | How to force an Index ? |
| Previous Message | Chris Miles | 2003-08-26 17:19:12 | postgresql and replication |