| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Andreas Karlsson <andreas(at)proxel(dot)se>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Supporting Windows SChannel as OpenSSL replacement |
| Date: | 2014-08-14 18:16:23 |
| Message-ID: | CA+TgmoZoHuHnLX_SsSey8_=f8A3x-A9yf40iAE9NeVhrNKUnmw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 12, 2014 at 1:52 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-08-14 18:19:13 | Re: Function to know last log write timestamp |
| Previous Message | Bruce Momjian | 2014-08-14 18:13:44 | Re: jsonb format is pessimal for toast compression |