| From: | Melvin Davidson <melvin6925(at)gmail(dot)com> |
|---|---|
| To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Multiple databases and shared_buffers |
| Date: | 2016-02-18 02:50:57 |
| Message-ID: | CANu8Fiww9QgBs7+varr36+FUJtZCqJ4hePY3SdPnHmmAquzqiA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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 <pierce(at)hogranch(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Smith | 2016-02-18 05:32:11 | BRIN Usage |
| Previous Message | John R Pierce | 2016-02-17 22:21:49 | Re: Multiple databases and shared_buffers |