| From: | Alfred Perlstein <alfred(at)freebsd(dot)org> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Perfomance degradation 9.3 (vs 9.2) for FreeBSD |
| Date: | 2014-04-21 16:01:41 |
| Message-ID: | 535540E5.4070508@freebsd.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4/21/14 8:58 AM, Tom Lane wrote:
> Andres Freund <andres(at)2ndquadrant(dot)com> writes:
>> On 2014-04-21 11:45:49 -0400, Andrew Dunstan wrote:
>>> That seems to make more sense. I can't imagine why this would be a runtime
>>> parameter as opposed to build time.
>> Because that implies that packagers and porters need to make that
>> decision. If it's a GUC people can benchmark it and decide.
> As against that, the packager would be more likely to get it right
> (or even to know that there's an issue).
Can the package builder not set the default for the runtime tunable?
Honestly we're about to select a db platform for another FreeBSD based
system we are building, I strongly hoping that we can get back to
sysvshm easily otherwise we may have to select another store.
-Alfred (who still remembers back when Tom had a login on our primary db
to help us. :) )
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-04-21 16:11:51 | Re: Perfomance degradation 9.3 (vs 9.2) for FreeBSD |
| Previous Message | Alfred Perlstein | 2014-04-21 15:59:42 | Re: Perfomance degradation 9.3 (vs 9.2) for FreeBSD |