Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Subject: Re: Read performance on Large Table
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <CA+ebzukaZJVOjw2Vqg0cuCUqbaEEHHuCa-pNbsX6CWAZyga3Fw@mail.gmail.com>
Date: Thu, 21 May 2015 09:09:26 -0600
Cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <CA5B0736-CD74-4751-87DA-875D5743A003@elevated-dev.com>
References: 
 <CA+ebzukaZJVOjw2Vqg0cuCUqbaEEHHuCa-pNbsX6CWAZyga3Fw@mail.gmail.com>
To: Kido Kouassi <jjkido@gmail.com>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

On May 21, 2015, at 8:54 AM, Kido Kouassi <jjkido@gmail.com> wrote:
>=20
> 2: Create an index on the Timestamp column sin it is the one we use the m=
ost in queries.

Absolutely. Go ahead right now.

Note that you can use the CONCURRENTLY option to create index, and it will =
not require a lock on the table, so you can do it while the db is being use=
d. It takes longer, sometimes a lot longer, than the regular create, but wh=
o cares? Start it and leave it.

After you=E2=80=99ve done that and seen how much benefit you get just from =
indexing your most-commonly used column, post a range of common queries bac=
k here for further advice.

--=20
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice


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