Re: Supporting Windows SChannel as OpenSSL replacement - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Supporting Windows SChannel as OpenSSL replacement
Date
Msg-id CA+TgmoZoHuHnLX_SsSey8_=f8A3x-A9yf40iAE9NeVhrNKUnmw@mail.gmail.com
Whole thread Raw
In response to Re: Supporting Windows SChannel as OpenSSL replacement  (Heikki Linnakangas <hlinnakangas@vmware.com>)
List pgsql-hackers
On Tue, Aug 12, 2014 at 1:52 PM, Heikki Linnakangas
<hlinnakangas@vmware.com> wrote:
> This isn't a showstopper, but needs some thought. As the patch stands, it
> uses a single key container called "PostgreSQL server key container", and
> makes no attempt to delete the keys after they're no longer used. That
> works, but it leaves the key lying on the system.

What about using something like 'PostgreSQL ' || system_identifier?

Would it make sense to have pg_ctl unregister delete the key
container, or do we need a separate facility for that?

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: jsonb format is pessimal for toast compression
Next
From: Robert Haas
Date:
Subject: Re: Function to know last log write timestamp