Brian Ferhle wrote:
> I've got a situation where I need to increase
> max_pred_locks_per_transaction value to allow the addition of a
> slony node to complete on postgres 9.1. We had this issue before
> and we increased the default value from 64 to 128, but now we have
> a sync that takes even l
Hi all,
I've got a situation where I need to increase max_pred_locks_per_transaction
value to allow the addition of a slony node to complete on postgres 9.1. We had
this issue before and we increased the default value from 64 to 128, but now we
have a sync that takes even longer and the value f
"Fred Parkinson" wrote:
> 2. Is there way to tell psql NOT to clear the screen, so I can
> subsequently view it while I work?
\pset pager off
-Kevin
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pg
On Tue, May 8, 2012 at 8:57 AM, Tim Bruce - Postgres
wrote:
> On Tue, May 8, 2012 07:28, Fred Parkinson wrote:
>> I am currently using postgresql version 9.1.3
>>
>> In the past, when I ran psql and needed useful information provided by
>> commands like \h or \d, the information was presented on t
On Tue, May 8, 2012 07:28, Fred Parkinson wrote:
> I am currently using postgresql version 9.1.3
>
> In the past, when I ran psql and needed useful information provided by
> commands like \h or \d, the information was presented on the screen and I
> could proceed with further commands while viewing
"Gnanakumar" wrote:
> our web-based application has crossed more than 500 concurrent
> users. Hence we've already upgraded RAM and now we want to
> upgrade max connection parameter too. Yes, we're already using
> pgpool-II v3.1.1 for connection pooling.
The main point of using a connection p
I am currently using postgresql version 9.1.3
In the past, when I ran psql and needed useful information provided by commands
like \h or \d, the information was presented on the screen and I could proceed
with further commands while viewing the information.
Now I need to hit -q to get out of
On Tue, 8 May 2012 14:56:52 +0530, Gnanakumar wrote:
As you can see, in my case, I'm setting only 3 GB (3072 MB), which is
actually below 8 GB. So, I need to increase kernel parameters in
this
case. Any ideas/insights?
I am not using CentOS (or Linux at all), but
edit /etc/sysctl.conf
and
> did you read
> http://www.postgresql.org/docs/8.2/static/kernel-resources.html ?
Yes, I read. But I'm not able to find a correct way to increase Linux
Kernel parameters.
> If it is a dedicated DB server the rule of thumb usually is to use
> 25% RAM for shared buffers, but no more than 8GB unl
Hi Gnanam,
On Tue, 8 May 2012 12:22:58 +0530, Gnanakumar wrote:
Our Production server has got 35 GB physical RAM size. Since the
server
has lots of RAM, we want to really make use of it. We've already
configured
"max_connections" to 1000 and "shared_buffers" to 1536 MB, but when
we tried
t
10 matches
Mail list logo
