From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
---|---|
To: | Greg Stark <gsstark(at)mit(dot)edu> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, pgsql-hackers(at)postgresql(dot)org, Andrew Dunstan <andrew(at)dunslane(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, aly(dot)dharshi(at)telus(dot)net, Peter Eisentraut <peter_e(at)gmx(dot)net> |
Subject: | Re: initdb profiles |
Date: | 2005-09-11 17:20:48 |
Message-ID: | 20050911172048.GB7630@pervasive.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Sep 11, 2005 at 12:15:01PM -0400, Greg Stark wrote:
> > It'd be nice to get out from under the fixed-size-shmem restriction, but
> > I don't know any very portable way to do that.
>
> Without knowing that part of the code at all it seems to me the logical
> approach would be to make the fsm steal its pages out of the shared buffers
> allocation. That is, you specify a total amount of shared memory to allocate
> and Postgres decides how much of it to use for shared buffers and how much for
> fsm.
FWIW, I know this is how DB2 does things, and I think Oracle's the same.
We probably still want some kind of limit so it doesn't blow the buffer
cache completely out.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-09-11 18:01:46 | Re: random system table corruption ... |
Previous Message | Peter Eisentraut | 2005-09-11 17:11:18 | Re: -fPIC |