On Mar 26, 2010, at 5:25 PM, Scott Carey wrote:
> Linux until recently does not account for shared memory properly in its swap
> 'aggressiveness' decisions.
> Setting shared_buffers larger than 35% is asking for trouble.
>
> You could try adjusting the 'swappiness' setting on the fly and seeing
Hi All,
Example on optimizer
===
postgres=# create table test(id int);
CREATE TABLE
postgres=# insert into test VALUES (1);
INSERT 0 1
postgres=# select * from test;
id
1
(1 row)
postgres=# explain select * from test;
QUERY PLAN
--
Hi,
I am using pgbench for running tests on PostgreSQL.
I have a few questions;
1) For calculating time to get the TPS, is pgbench using the wall
clock time or cpu time?
2)How is TPS calculated?
Thanks in advance,
Reydan
--
Sent via pgsql-performance mailing list (pgsql-performance@postgres
1. VACUUM FULL ANALYZE once in a week during low-usage time and
VACUUM FULL compacts tables, but tends to bloat indexes. Running it weekly
is NOT RECOMMENDED.
A correctly configured autovacuum (or manual vacuum in some circumstances)
should maintain your DB healthy and you shouldn't ne
On 03/27/2010 08:00 AM, Gnanakumar wrote:
Hi,
We're using PostgreSQL 8.2. Recently, in our production database, there
was a severe performance impact.. Even though, we're regularly doing both:
1. VACUUM FULL ANALYZE once in a week during low-usage time and
2. ANALYZE everyday at low-usage time
Hi,
We're using PostgreSQL 8.2. Recently, in our production database, there was
a severe performance impact.. Even though, we're regularly doing both:
1. VACUUM FULL ANALYZE once in a week during low-usage time and
2. ANALYZE everyday at low-usage time
Also, we noticed that the
