| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Andrew Dunstan <andrew(dot)dunstan(at)2ndquadrant(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ssl passphrase callback |
| Date: | 2019-11-08 14:12:08 |
| Message-ID: | CANP8+jKGDEmSmjZwwjqqMsWSLRqTVc5qLwk_xMvR7PH9jNLiBw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 7 Nov 2019 at 10:24, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> What is the value of a shared library over a shell command? We had this
> discussion in relation to archive_command years ago, and decided on a
> shell command as the best API.
>
I don't recall such a discussion, but I can give perspective:
* shell command offered the widest and simplest API for integration, which
was the most important consideration for a backup API. That choice caused
difficulty with the need to pass information to the external command, e.g.
%f %p
* shared library is more appropriate for a security-related module, so
users can't see how it is configured, as well as being more
tightly integrated so it can be better tailored to various uses
Summary is that the choice is not random, nor mere preference
--
Simon Riggs http://www.2ndQuadrant.com/
<http://www.2ndquadrant.com/>
PostgreSQL Solutions for the Enterprise
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2019-11-08 14:16:37 | Re: add a MAC check for TRUNCATE |
| Previous Message | Julien Rouhaud | 2019-11-08 14:10:57 | Re: Monitoring disk space from within the server |