pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feedPriority to a mission critical transaction
3+ messages / 3 participants
[nested] [flat]
* Priority to a mission critical transaction
@ 2006-11-21 23:43 Carlos H. Reimer <carlos.reimer@opendb.com.br>
0 siblings, 1 reply; 3+ messages in thread
From: Carlos H. Reimer @ 2006-11-21 23:43 UTC (permalink / raw)
To: pgsql-performance
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
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Priority to a mission critical transaction
@ 2006-11-23 20:40 Brad Nicholson <bnichols@ca.afilias.info>
parent: Carlos H. Reimer <carlos.reimer@opendb.com.br>
0 siblings, 1 reply; 3+ messages in thread
From: Brad Nicholson @ 2006-11-23 20:40 UTC (permalink / raw)
To: carlos.reimer@opendb.com.br; +Cc: 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.
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Priority to a mission critical transaction
@ 2006-11-27 00:51 Jim C. Nasby <jim@nasby.net>
parent: Brad Nicholson <bnichols@ca.afilias.info>
0 siblings, 0 replies; 3+ messages in thread
From: Jim C. Nasby @ 2006-11-27 00:51 UTC (permalink / raw)
To: Brad Nicholson <bnichols@ca.afilias.info>; +Cc: carlos.reimer@opendb.com.br; 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@nasby.net
EnterpriseDB http://enterprisedb.com 512.569.9461 (cell)
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2006-11-27 00:51 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-11-21 23:43 Priority to a mission critical transaction Carlos H. Reimer <carlos.reimer@opendb.com.br>
2006-11-23 20:40 ` Brad Nicholson <bnichols@ca.afilias.info>
2006-11-27 00:51 ` Jim C. Nasby <jim@nasby.net>
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