| From: | Nikolas Everett <nik9000(at)gmail(dot)com> |
|---|---|
| To: | François Beausoleil <francois(at)teksol(dot)info> |
| Cc: | "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: explain analyze reports that my queries are fast but they run very slowly |
| Date: | 2012-12-27 18:00:24 |
| Message-ID: | CAPmjWd2PTkOfRLFyQ0tfp0dXUb3_GfQO9T2U0m95ejA4sw5LHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Actually that last paragraph doesn't make much sense. Please ignore it.
On Thu, Dec 27, 2012 at 12:58 PM, Nikolas Everett <nik9000(at)gmail(dot)com> wrote:
> New news - the hot slave seems to be performing as expected with no long
> pauses.
>
> It looks like we're using an archive_timeout of 60 seconds and default
> checkout_timeout and checkpoint_completion_target. I didn't do any of the
> research on this. It seems like we're asking postgres to clear all of the
> dirty buffers every 60 seconds. With 48 gigs of shared buffers we could
> have quite a few buffers to clear. Is there some place I could check on
> how all that is going?
>
> On Thu, Dec 27, 2012 at 12:45 PM, Nikolas Everett <nik9000(at)gmail(dot)com>wrote:
>
>> p
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Janes | 2012-12-27 18:07:17 | Re: Why does the query planner use two full indexes, when a dedicated partial index exists? |
| Previous Message | Nikolas Everett | 2012-12-27 17:58:33 | Re: explain analyze reports that my queries are fast but they run very slowly |