Re: controlling the location of server-side SSL files

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: controlling the location of server-side SSL files
Date: 2012-01-03 04:42:03
Message-ID: 9434.1325565723@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> On mn, 2012-01-02 at 15:47 +0100, Magnus Hagander wrote:
>> Were you thinking one option pointing to a directory or one option per
>> file?

> One option per file:

That seems like serious overkill. Why not one option specifying the
directory? What use-case is there for letting them be in different
directories, let alone letting the DBA choose random names for each one?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2012-01-03 04:44:49 Re: spinlocks on powerpc
Previous Message Noah Misch 2012-01-03 04:40:38 Re: ALTER TABLE lock strength reduction patch is unsafe