Date: Mon, 2 Feb 2015 15:28:30 +0000 (UTC)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
To: Naresh Soni <jmnaresh@gmail.com>
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Message-ID: <1838847801.550314.1422890910146.JavaMail.yahoo@mail.yahoo.com>
In-Reply-To: 
 <CADg8u6=smhK4+DREEMKUSM+hDnbr2FAGE4t-1vomB383ERsYtw@mail.gmail.com>
References: 
 <CADg8u6=smhK4+DREEMKUSM+hDnbr2FAGE4t-1vomB383ERsYtw@mail.gmail.com>
Subject: Re: Hi Community
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Length: 762
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Naresh Soni <jmnaresh@gmail.com> wrote:

> So you mean postgres can handle such huge records without any
> fine tuning required on postgres

For any non-trivial database you will certainly need to make
adjustments to the configuration files, and probably to the OS,
too.  You may want to pay for some advice from one of the companies
with people experienced in tuning PostgreSQL, but you can get a
good start on things with the advice on this Wiki page:

https://wiki.postgresql.org/wiki/Tuning_Your_PostgreSQL_Server

You should also familiarize yourself with the PostgreSQL
documentation on the topic:

http://www.postgresql.org/docs/current/interactive/runtime-config.html

--
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