Re: ssl passphrase callback
Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
From: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
To: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Bruce Momjian <bruce@momjian.us>, Magnus Hagander <magnus@hagander.net>,
Tomas Vondra <tomas.vondra@2ndquadrant.com>,
Simon Riggs <simon@2ndquadrant.com>, Robert Haas <robertmhaas@gmail.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2019-11-15T13:59:45Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Provide a TLS init hook
- 896fcdb230e7 13.0 landed
On 11/14/19 3:21 PM, Alvaro Herrera wrote: > On 2019-Nov-14, Andrew Dunstan wrote: > >> I guess this would work. There would have to be a deal of code to load >> the library and lookup the symbol. Do we really think it's worth it? >> Leveraging shared_preload_libraries makes this comparatively simple. > Using the generic interface has the drawback that the user can make more > mistakes. I think that's part of Bruce's issue with it (although I may > misinterpret.) > > I think if you add most of it as a new entry point in dfmgr.c (where you > can leverage internal_library_load) and returns a function pointer to > the user specified function, it's all that much additional code. > > (I don't think you can use load_external_function as is, because it > assumes fmgr V1 calling convention, which I'm not sure serves your case. > But then maybe it does. And if not, then those 10 lines should be very > similar to the code you'd need to add.) In the absence of further comment I will try to code up something along these lines. cheers andrew -- Andrew Dunstan https://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services