On Thu, Feb 18, 2016 at 05:38:45PM -0500, Melvin Davidson wrote:
> From your questions, it appears you are a little weak on PostgreSQL
> Database Administration. I respectfully suggest you obtain a copy of the
> following book to get a clearer understandings of how things work.
The PostgreSQL doc
//www.postgresql.org/docs/9.5/interactive/functions-admin.html#FUNCTIONS-ADMIN-SIGNAL
-Original Message-
From: Melvin Davidson
To: Rakesh Kumar ; pgsql-general
Sent: Thu, Feb 18, 2016 4:12 pm
Subject: Re: [GENERAL] Multiple databases and shared_buffers
>What do you mean that t
gt; Sent: Thu, Feb 18, 2016 4:12 pm
> Subject: Re: [GENERAL] Multiple databases and shared_buffers
>
> >What do you mean that the data is actually not stored in the shared
> buffer.
> >From the link you provided :
> >"The “shared_buffers” configuration parameter determines
temporarily, it will be great.
-Original Message-
From: Melvin Davidson
To: Rakesh Kumar ; pgsql-general
Sent: Thu, Feb 18, 2016 4:12 pm
Subject: Re: [GENERAL] Multiple databases and shared_buffers
>What do you mean that the data is actually not stored in the shared buffer.
>Fr
>What do you mean that the data is actually not stored in the shared
buffer.
>From the link you provided :
>"The “shared_buffers” configuration parameter determines how much memory
>is dedicated to PostgreSQL to use for caching data."
Again, you misunderstand. Cached data (and queries) is for shar
On 2/18/2016 12:04 PM, Rakesh Kumar wrote:
NOTE: It is very important you provide the version of PostgreSQL and
O/S when addressing this mail list.
Since it is a new project, we are going with:
PG: 9.5.1
OS: RHEL 6.4
off topic for this list, but RHEL 6.4 was a 'snapshot' 3 years ago, and
i
NOTE: It is very important you provide the version of PostgreSQL and O/S when
addressing this mail list.
Since it is a new project, we are going with:
PG: 9.5.1
OS: RHEL 6.4
What do you mean that the data is actually not stored in the shared buffer.
>From the link you provided :
"The “shared_buffers” configuration parameter determines how much memory
is dedicated to PostgreSQL to use for caching data."
This seems to be the same like other RDBMS. Typically the termi
ly.
> That's why I brought this up. Personally I don't think this is a serious
> limitation at all.
>
>
>
>
> -Original Message-
> From: Melvin Davidson
> To: pgsql-general
> Sent: Wed, Feb 17, 2016 9:53 pm
> Subject: Re: [GENERAL] Multiple
this is a serious limitation at
all.
-Original Message-
From: Melvin Davidson
To: pgsql-general
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_b
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 wrote:
> On 2/17/2016 6:54 AM, Data Cruncher 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
On Thu, Feb 18, 2016 at 1: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.
shared_buffers parameter is for the whol
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.
thanks.
14 matches
Mail list logo
