| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | postgresbugs <postgresbugs(at)grifent(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: PGPASSWORD |
| Date: | 2005-02-25 23:34:24 |
| Message-ID: | 421FB600.90909@hogranch.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
postgresbugs wrote:
>
>
> Tom Lane wrote:
>
>> Agreed, which is why we invented .pgpass. But that argument scales up
>> to beyond one invocation of this hypothetical script, does it not?
>>
>> regards, tom lane
>>
>>
> I guarantee you that his process which includes binaries and scripts is
> not hypothetical.
indeed. cronjobs come to mind as another candidate for this issue.
there's no easy answer, we've tried to deal with similar problems on Solaris
with Oracle, hiding command script passwords isn't easy.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | postgresbugs | 2005-02-26 03:51:47 | Re: PGPASSWORD |
| Previous Message | Oliver Jowett | 2005-02-25 23:27:38 | Re: PGPASSWORD |