[prev in list] [next in list] [prev in thread] [next in thread] 

List:       pgsql-performance
Subject:    Re: [PERFORM] Heavy contgnous load
From:       Pavel Stehule <pavel.stehule () gmail ! com>
Date:       2011-11-13 8:57:31
Message-ID: CAFj8pRA=871vLwT+4DWaMKbqVK60JWqUjFD2eu23dDe+ypeJsw () mail ! gmail ! com
[Download RAW message or body]

Hello

2011/11/9 kzsolt <kzsoltkzsolt@freemail.hu>:
> I try to found out more information. Looks like the COUNT(*) is not the
> strongest part of pgr therfore I do a worakround. After this I have the
> folwing result:
> 
> Below the 1Mrec the row insert time is ~23msec. Above the 7Mrec the insert
> time is ~180msec.
> 

* use a copy statement
* use a explicit transaction
* if you can disable triggers (and RI)
* if you cannot and use a RI, unsures a indexes on PK and FK

Regards

Pavel Stehule


> I belive I use the fastest index type (default).
> 
> So any idea to make postgres faster at higher number of records?
> 
> 
> --
> View this message in context: \
> http://postgresql.1045698.n5.nabble.com/Heavy-contgnous-load-tp4913425p4978893.html \
> Sent from the PostgreSQL - performance mailing list archive at Nabble.com. 
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
> 

-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance


[prev in list] [next in list] [prev in thread] [next in thread]