Date: Mon, 2 Feb 2015 14:32:45 +0000 (UTC)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
To: Naresh Soni <jmnaresh@gmail.com>,
 "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: <1123309468.541729.1422887565854.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: 
 <CADg8u6kEOrqzmVE8BY34RAE_XzxQE9ZvjFz--v1q7jZNxj58wg@mail.gmail.com>
References: 
 <CADg8u6kEOrqzmVE8BY34RAE_XzxQE9ZvjFz--v1q7jZNxj58wg@mail.gmail.com>
Subject: Re: Hi Community
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Length: 1059
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Naresh Soni <jmnaresh@gmail.com> wrote:

> This is my first question on the list, I wanted to ask if
> postgres can handle multi millions records? for example there
> will be 1 million records per table per day, so 365 millions per
> year.

Yes, I have had hundreds of millions of rows in a table without
performance problems. If you want to see such a table in action,
go to the following web site, bring up a court case, and click the
"Court Record Events" button. Last I knew the table containing
court record events had about 450 million rows, with no
partitioning.  The total database was 3.5 TB.

http://wcca.wicourts.gov/

> Is yes, then please elaborate.

You will want indexes on columns used in the searches. Depending
on details you have not provided it might be beneficial to
partition the table. Do not consider partitioning to be some
special magic which always makes things faster, though -- it can
easily make performance much worse if it is not a good fit.

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


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