| From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
|---|---|
| To: | Alex Thurlow <alex(at)blastro(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Tuning resource parameters for a logging database. |
| Date: | 2009-05-21 19:42:29 |
| Message-ID: | dcc563d10905211242p5b17fa35xb8968bed430ed1ae@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, May 21, 2009 at 1:39 PM, Alex Thurlow <alex(at)blastro(dot)com> wrote:
> I should also specify how my inserts are happening I guess. I'm actually
> doing the logs to flat files and then inserting them into the database on an
> hourly basis using COPY, so I don't need to worry as much about the log
> insert speed as I do the reporting.
Cool. Then definitely look at partitioning, and also start running
explain analyze on your longer running queries. You'll often find
some part of the plan that makes no sense (usually a difference
between estimated and actual returned rows is a clue). You can earn a
lot of performance by tuning your queries in this way.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Karl Nack | 2009-05-21 19:57:43 | After each row trigger NOT seeing data changes? |
| Previous Message | Scott Marlowe | 2009-05-21 19:39:19 | Re: Tuning resource parameters for a logging database. |