From: Robert Haas <robertmhaas@gmail.com>
To: Jaime Casanova <jcasanov@systemguards.com.ec>
Cc: psql performance list <pgsql-performance@postgresql.org>
Subject: Re: measure database contention
Date: Wed, 17 Dec 2008 11:56:56 -0500
Message-ID: <603c8f070812170856g7ae06d58q2f487bead5f7be15@mail.gmail.com> (raw)
In-Reply-To: <3073cc9b0812170738v69e43d89r8d6dae87453b4993@mail.gmail.com>
References: <3073cc9b0812161132w3ae157a8n69e2b0cccea05ca2@mail.gmail.com>
<603c8f070812170618g3116a90du94cbf102f0336d59@mail.gmail.com>
<3073cc9b0812170738v69e43d89r8d6dae87453b4993@mail.gmail.com>
> is the exact query... i think it will be removed later today because
> is a bad query anyway... but my fear is that something like happens
> even with good ones...
>
> maybe chekpoints could be the problem?
> i have 8.3.5 and condigured checkpoint_timeout in 15 minutes,
> chekpoint_segments 6 and checkpoint_completion_target to 0.5
Well, it might help if you could provide the query, and the EXPLAIN output.
Unless the query is updating data (rather than just retrieving it),
checkpoints shouldn't be involved (I think).
...Robert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: robertmhaas@gmail.com, jcasanov@systemguards.com.ec
Subject: Re: measure database contention
In-Reply-To: <603c8f070812170856g7ae06d58q2f487bead5f7be15@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox