From: Jim C. Nasby <jim@nasby.net>
To: Brad Nicholson <bnichols@ca.afilias.info>
Cc: carlos.reimer@opendb.com.br
Cc: pgsql-performance@postgresql.org
Subject: Re: Priority to a mission critical transaction
Date: Sun, 26 Nov 2006 18:51:43 -0600
Message-ID: <20061127005143.GJ39519@nasby.net> (raw)
In-Reply-To: <1164314415.21439.32.camel@dba5.int.libertyrms.com>
References: <PEEPKDFEHHEMKBBFPOOKCEBMDJAA.carlos.reimer@opendb.com.br>
<1164314415.21439.32.camel@dba5.int.libertyrms.com>
On Thu, Nov 23, 2006 at 03:40:15PM -0500, Brad Nicholson wrote:
> On Tue, 2006-11-21 at 21:43 -0200, Carlos H. Reimer wrote:
> > Hi,
> >
> > We have an application that is mission critical, normally very fast,
> > but when an I/O or CPU bound transaction appears, the mission critical
> > application suffers. Is there a way go give some kind of priority to
> > this kind of application?
> > Reimer
>
>
> Not that I'm aware of. Depending on what the problems transactions are,
> setting up a replica on a separate machine and running those
> transactions against the replica might be the solution.
The BizGres project has been working on resource quotas, which might
eventually evolve to what you're looking for.
--
Jim Nasby jim@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
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: jim@nasby.net, bnichols@ca.afilias.info, carlos.reimer@opendb.com.br
Subject: Re: Priority to a mission critical transaction
In-Reply-To: <20061127005143.GJ39519@nasby.net>
* 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