From: | marcelo <marcelo(dot)nicolet(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: mild modification to pg_dump |
Date: | 2017-11-17 21:58:43 |
Message-ID: | 576ff009-5f3c-3b1f-4036-3cdbe597d148@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Again: knowing of .pgpass (thank you Scott) this is what I will do.
On 17/11/17 17:49, Ron Johnson wrote:
> On 11/17/2017 02:23 PM, 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.
>>
>
> Specifically, do you mean to write a simple daemon which forks pg_dump
> at the appropriate time?
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2017-11-17 23:38:41 | Re: mild modification to pg_dump |
Previous Message | marcelo | 2017-11-17 21:56:45 | Re: mild modification to pg_dump |