[PERFORM] Slow Performance on a XEON E5504

2012-08-27 Thread Felix Schubert
Hello List, I've got a system on a customers location which has a XEON E5504 @ 2.00GHz Processor (HP Proliant) It's postgres 8.4 on a Debian Squeeze System running with 8GB of ram: The Postgres Performance on this system measured with pgbench is very poor: transaction type: TPC-B (sort of)

[PERFORM] Investigating the reason for a very big TOAST table size

2012-08-27 Thread Liron Shiri
Hi, We have a table which its TOAST table size is 66 GB, and we believe should be smaller. The table size is 472 kb. And the table has 4 columns that only one of them should be toasted. The table has only 8 dead tuples, so apparently this is not the problem. This table contains a column with

[PERFORM] Execution from java - slow

2012-08-27 Thread Jayadevan M
Hello all, I have a plpgsql function that takes a few seconds (less than 5) when executed from psql. The same function, when invoked from java via a prepared statement takes a few minutes. There are a few queries in the function. Out of these, the first query takes input parameters for

Re: [PERFORM] Execution from java - slow

2012-08-27 Thread Albe Laurenz
Jayadevan M wrote: I have a plpgsql function that takes a few seconds (less than 5) when executed from psql. The same function, when invoked from java via a prepared statement takes a few minutes. There are a few queries in the function. Out of these, the first query takes input parameters for

Re: [PERFORM] Investigating the reason for a very big TOAST table size

2012-08-27 Thread Daniel Farina
On Sun, Aug 26, 2012 at 5:46 AM, Liron Shiri lir...@checkpoint.com wrote: Hi, We have a table which its TOAST table size is 66 GB, and we believe should be smaller. The table size is 472 kb. And the table has 4 columns that only one of them should be toasted. The table has only 8 dead

[PERFORM] Vacuum problems with 9.1

2012-08-27 Thread Nimesh Satam
Hi, We have been using the current version of postgres i.e. 9.1.4 with streaming replication on. While vacuuming we noticed that certain dead rows are not getting removed and following debug information is printed: DETAIL: 12560 dead row versions cannot be removed yet. As per suggestion, we