| From: | Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info> |
|---|---|
| To: | carlos(dot)reimer(at)opendb(dot)com(dot)br |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Priority to a mission critical transaction |
| Date: | 2006-11-23 20:40:15 |
| Message-ID: | 1164314415.21439.32.camel@dba5.int.libertyrms.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-performance |
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.
--
Brad Nicholson 416-673-4106
Database Administrator, Afilias Canada Corp.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | alfranio correia junior | 2006-11-24 11:53:24 | Re: [Replica-hooks-discuss] Integrating Replication ino |
| Previous Message | Markus Schiltknecht | 2006-11-23 17:26:12 | Re: [Replica-hooks-discuss] Integrating Replication ino |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gopal | 2006-11-23 22:37:08 | Postgres scalability and performance on windows |
| Previous Message | Greg Smith | 2006-11-23 18:09:54 | Re: Direct I/O issues |