From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
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 20:31:49 |
Message-ID: | CA+Tgmob4BKR5CPS_wfse2ntp2bvzQmcXVjGGR03f9DXfYQvjWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Jan 3, 2012 at 9:38 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.
No argument. I'm merely saying that I think the rationale for these
GUCs is solid enough to justify their existence.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Paul Ramsey | 2012-01-04 20:35:33 | Re: BUG #6379: SQL Function Causes Back-end Crash |
Previous Message | Robert Haas | 2012-01-04 20:27:50 | Re: Page Checksums + Double Writes |