From: | Ron Johnson <ron(dot)l(dot)johnson(at)cox(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: mild modification to pg_dump |
Date: | 2017-11-17 21:19:34 |
Message-ID: | 3f43162a-7d47-5ac6-de86-40f22cb06eac@cox.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
What about the pgpass file?
https://www.postgresql.org/docs/9.2/static/libpq-pgpass.html
On 11/17/2017 03:06 PM, marcelo wrote:
> I need to "emulate" the pg_dump code because the password prompt. Years
> ago I write a program (for the QnX environment) that catched some prompt
> and emulates the standard input. I don't like to do that again.
>
> On 17/11/17 17:23, John R Pierce wrote:
>> On 11/17/2017 12:19 PM, marcelo wrote:
>>> Sorry, I was not exact.
>>> I don't need nor like to change pg_dump. Rather, based on pg_dump code,
>>> I need to develop a daemon which can receive a TCP message (from a
>>> privileged app) containing some elements: the database to dump, the user
>>> under which do that, and his password. (My apps are using that same
>>> data, of course, encripted to the common users).
>>
>>
>> I would just fork pg_dump to do the actual dump rather than try and
>> incorporate its source code into your app.
>>
>
--
World Peace Through Nuclear Pacification
From | Date | Subject | |
---|---|---|---|
Next Message | Scott Mead | 2017-11-17 21:31:54 | Re: mild modification to pg_dump |
Previous Message | marcelo | 2017-11-17 21:19:01 | Re: mild modification to pg_dump |