| From: | Scott Ribe <scott_ribe(at)elevated-dev(dot)com> |
|---|---|
| To: | Kido Kouassi <jjkido(at)gmail(dot)com> |
| Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Read performance on Large Table |
| Date: | 2015-05-21 15:09:26 |
| Message-ID: | CA5B0736-CD74-4751-87DA-875D5743A003@elevated-dev.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On May 21, 2015, at 8:54 AM, Kido Kouassi <jjkido(at)gmail(dot)com> wrote:
>
> 2: Create an index on the Timestamp column sin it is the one we use the most 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 used. It takes longer, sometimes a lot longer, than the regular create, but who cares? Start it and leave it.
After you’ve done that and seen how much benefit you get just from indexing your most-commonly used column, post a range of common queries back here for further advice.
--
Scott Ribe
scott_ribe(at)elevated-dev(dot)com
http://www.elevated-dev.com/
https://www.linkedin.com/in/scottribe/
(303) 722-0567 voice
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Ribe | 2015-05-21 15:18:30 | Re: Read performance on Large Table |
| Previous Message | Scott Marlowe | 2015-05-21 15:05:37 | Re: Read performance on Large Table |