| From: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
|---|---|
| To: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
| Cc: | carlos(dot)reimer(at)opendb(dot)com(dot)br, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Priority to a mission critical transaction |
| Date: | 2006-11-27 00:51:43 |
| Message-ID: | 20061127005143.GJ39519@nasby.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-performance |
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(at)nasby(dot)net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Bernier | 2006-11-27 03:05:09 | Re: pg_live-2.1.1 beta |
| Previous Message | Josh Berkus | 2006-11-26 23:07:09 | Re: pg_live-2.1.1 beta |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-11-27 01:01:35 | Re: When to vacuum a table? |
| Previous Message | Jim C. Nasby | 2006-11-26 23:41:02 | Re: Postgres server crash |