| 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 20:49:47 |
| Message-ID: | 5ba7371f-9616-0a34-6315-5a03b95f609b@cox.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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?
--
World Peace Through Nuclear Pacification
| From | Date | Subject | |
|---|---|---|---|
| Next Message | marcelo | 2017-11-17 21:06:56 | Re: mild modification to pg_dump |
| Previous Message | Justin Pryzby | 2017-11-17 20:41:50 | Re: unnest-like pg_stats.most_common_values and pg_stats.most_common_freqs |