It is a business requirement that we store our clients data in separate
databases. Our sales folks insist it is non negotiable. Our current technology
does
support that and also maintain buffer pools for each db independently. That's
why I brought this up. Personally I don't think this is a serious limitation at
all.
-----Original Message-----
From: Melvin Davidson <melvin6...@gmail.com>
To: pgsql-general <pgsql-general@postgresql.org>
Sent: Wed, Feb 17, 2016 9:53 pm
Subject: Re: [GENERAL] Multiple databases and shared_buffers
I think this begs the question "Why do you think you need to separate the
shared_buffers"?
What version of PostgreSQL are you using?
What is your O/S?
How many CPU's on your server?
How much memory?
On Wed, Feb 17, 2016 at 5:21 PM, John R Pierce <pie...@hogranch.com> wrote:
On 2/17/2016 6:54 AM, Data Cruncher wrote:
We will be creating multiple databases in a cluster (instance). Is there
any way to separate shared_buffers for each database? Looks like
not since PG does not allow user created shared buffers.
you would need to run multiple instances if you feel you need that level
of control over shared_buffers.
--
john r pierce, recycling bits in santa cruz
--
Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
