Hi,
On 05/29/15 11:51, Peter J. Holzer wrote:
A couple of additional observations:
The total cost of both queries is quite similar, so random variations
might push into one direction or the other. Indeed, after dropping
and recreating indexes (I tried GIN indexes as suggested by Heikki on
[1])
On 05/29/15 20:10, Ashik S L wrote:
Hi All,
I am using postgresDB on redhat machine which is having 4GB RAM
machine. As soon as it starts to Inserting rows into the postgres DB
it will reach 100%cpu. It will comedown to normal after 40 minutes. I
tried perform some tuning on the postgres DB, B
> machine. As soon as it starts to Inserting rows into the postgres DB it
> will reach 100%cpu. It will comedown to normal after 40 minutes. I tried
> perform
How many rows are you inserting at once? How (sql insert? copy? \copy? using a
temp or unlogged table?)?
--
http://yves.zioup.com
gpg:
Hi All,
I am using postgresDB on redhat machine which is having 4GB RAM
machine. As soon as it starts to Inserting rows into the postgres DB it
will reach 100%cpu. It will comedown to normal after 40 minutes. I tried perform
some tuning on the postgres DB, But result was same.I am not postgres
DB
Hi All,
I am using postgresDB on redhat machine which is having 4GB RAM
machine. As soon as it starts to Inserting rows into the postgres DB it
will reach
100%cpu. It will comedown to normal after 40 minutes. I tried perform
some tuning on the postgres DB, But result was same.I am not postgres
DB
On 2015-05-29 10:55:44 +0200, Peter J. Holzer wrote:
> wdsah=> explain analyze select facttablename, columnname, term, concept_id,
> t.hidden, language, register
> from term t where facttablename='facttable_stat_fta4' and
> columnname='einheit' and exists (select 1 from facttable_stat_ft
wdsah=> select version();
version
---
PostgreSQL 9.1.15 on x86_64-unknown-linux-gnu, compiled by gcc (Debian
4.7.2-5
