Re: mild modification to pg_dump

From: John R Pierce <pierce(at)hogranch(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: mild modification to pg_dump
Date: 2017-11-17 20:23:52
Message-ID: d9a6f716-405d-3943-1071-716fbc1fdfc4@hogranch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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.

--
john r pierce, recycling bits in santa cruz

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Luca Ferrari 2017-11-17 20:32:23 unnest-like pg_stats.most_common_values and pg_stats.most_common_freqs
Previous Message marcelo 2017-11-17 20:19:08 Re: mild modification to pg_dump