Date: Thu, 12 Feb 2015 22:38:01 +0000 (UTC)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
To: Nico Sabbi <nicola.sabbi@poste.it>,
 "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
Message-ID: <2034701464.2446674.1423780681188.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: <54DD2872.3070603@poste.it>
References: <54DD2872.3070603@poste.it>
Subject: Re: Configuration tips for very large database
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Length: 650
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

Nico Sabbi <nicola.sabbi@poste.it> wrote:

> Queries get executed very very slowly, say 20 minutes.

> I'd like to know if someone has already succeeded in running
> postgres with 200-300M records with queries running much faster
> than this.

If you go to the http://wcca.wicourts.gov/ web site, bring up any
case, and click the "Court Record Events" button, it will search a
table with hundreds of millions of rows.  The table is not
partitioned, but has several indexes on it which are useful for
queries such as the one that is used when you click the button.

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


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