From: | Alex Thurlow <alex(at)blastronetworks(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Tuning resource parameters for a logging database. |
Date: | 2009-05-21 19:37:00 |
Message-ID: | 4A15AD5C.3030803@blastronetworks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I was hoping to not have to change all my code to automate the
partitioning table creation stuff, but if that's really the best way,
I'll check it out. Thanks for the advice.
Alex Thurlow
Blastro Networks
http://www.blastro.com
http://www.roxwel.com
http://www.yallwire.com
On 5/21/2009 2:24 PM, Vick Khera wrote:
> On Thu, May 21, 2009 at 3:13 PM, Alex Thurlow<alex(at)blastro(dot)com> wrote:
>
>> I have a postgresql database that I'm using for logging of data. There's
>> basically one table where each row is a line from my log files. It's
>> getting to a size where it's running very slow though. There are about 10
>> million log lines per day and I keep 30 days of data in it. All the columns
>>
>
> Are you using partitioning on this table? Your use case is literally
> the exact example everyone uses to show how to do partitioning on
> tables.
>
> Since you mostly scan on date, this will speed up your queries significantly.
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Thurlow | 2009-05-21 19:39:05 | Re: Tuning resource parameters for a logging database. |
Previous Message | Scott Marlowe | 2009-05-21 19:36:42 | Re: Tuning resource parameters for a logging database. |