From: | David Gilbert <dgilbert(at)velocet(dot)ca> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Thomas O'Connell" <tfo(at)monsterlabs(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: performance tuning: shared_buffers, sort_mem; swap |
Date: | 2002-08-13 22:48:38 |
Message-ID: | 15705.36038.645823.820155@canoe.velocet.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
>>>>> "Tom" == Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:
[on shared memory size, deleted]
Tom> There are also a number of fixed-size data structures in shared
Tom> memory, and I believe we throw on a 10% fudge factor for good
Tom> luck after we're done counting up what we think we need.
Tom> You could work out the effective multipliers for these parameters
Tom> with a little bit of experimental effort...
I don't often ask a question, but it's been bugging me for some time:
is there any reason why PostgreSQL must use SysV shared memory?
Coming from the BSD camp, I've often pondered why it doesn't use
BSD-style shared memory (which is often easier to allocate in the BSD
world).
Dave.
--
============================================================================
|David Gilbert, Velocet Communications. | Two things can only be |
|Mail: dgilbert(at)velocet(dot)net | equal if and only if they |
|http://daveg.ca | are precisely opposite. |
=========================================================GLO================
From | Date | Subject | |
---|---|---|---|
Next Message | Tim Ellis | 2002-08-14 00:09:18 | tedia2sql 1.2.4 released |
Previous Message | Tom Lane | 2002-08-13 22:17:38 | Re: performance tuning: shared_buffers, sort_mem; swap |