Re: controlling the location of server-side SSL files

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Peter Eisentraut <peter_e(at)gmx(dot)net>, 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-04 02:38:38
Message-ID: 2281.1325644718@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Tue, Jan 3, 2012 at 6:25 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> [ reasons ]

> I agree with these reasons. We don't get charged $0.50 per GUC, so
> there's no particular reason to contort things to have fewer of them.

Well, there definitely is a distributed cost to each additional GUC.
Peter's given what are probably adequate reasons to add several of them
here, but that doesn't mean we should not ask the question whether each
new GUC is really necessary.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jim Nasby 2012-01-04 03:59:03 Re: Should I implement DROP INDEX CONCURRENTLY?
Previous Message Tom Lane 2012-01-04 02:28:16 Re: pg_internal.init and an index file have the same inode