Re: Priority to a mission critical transaction
От
Brad Nicholson
Тема
Re: Priority to a mission critical transaction
Дата
Msg-id
1164314415.21439.32.camel@dba5.int.libertyrms.com
Ответ на
Priority to a mission critical transaction (Carlos H. Reimer)
Список
Дерево обсуждения
Priority to a mission critical transaction "Carlos H. Reimer" <carlos.reimer@opendb.com.br>
Re: Priority to a mission critical transaction Brad Nicholson <bnichols@ca.afilias.info>
Re: Priority to a mission critical transaction "Jim C. Nasby" <jim@nasby.net>
RES: Priority to a mission critical transaction "Carlos H. Reimer" <carlos.reimer@opendb.com.br>
Re: RES: Priority to a mission critical transaction Andreas Kostyrka <andreas@kostyrka.org>
Re: RES: Priority to a mission critical transaction Josh Berkus <josh@agliodbs.com>
Re: RES: Priority to a mission critical transaction Mark Kirkwood <markir@paradise.net.nz>
Re: RES: Priority to a mission critical transaction Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: RES: Priority to a mission critical transaction Mark Kirkwood <markir@paradise.net.nz>
Re: RES: Priority to a mission critical transaction Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: RES: Priority to a mission critical transaction Tom Lane <tgl@sss.pgh.pa.us>
Re: RES: Priority to a mission critical transaction Bruce Momjian <bruce@momjian.us>
Re: RES: Priority to a mission critical transaction Josh Berkus <josh@agliodbs.com>
Re: RES: Priority to a mission critical transaction Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: RES: Priority to a mission critical transaction Brian Hurt <bhurt@janestcapital.com>
Re: RES: Priority to a mission critical transaction Mark Lewis <mark.lewis@mir3.com>
Re: RES: Priority to a mission critical transaction Brian Hurt <bhurt@janestcapital.com>
Re: RES: Priority to a mission critical transaction Ron Mayer <rm_pg@cheapcomplexdevices.com>
Re: RES: Priority to a mission critical transaction Brian Hurt <bhurt@janestcapital.com>
Re: RES: Priority to a mission critical transaction Ron Mayer <rm_pg@cheapcomplexdevices.com>
Postgres and really huge tables Brian Hurt <bhurt@janestcapital.com>
Re: Postgres and really huge tables Scott Marlowe <smarlowe@g2switchworks.com>
Re: [pgsql-advocacy] Postgres and really huge tables "Joshua D. Drake" <jd@commandprompt.com>
Re: [pgsql-advocacy] Postgres and really huge tables Chris Mair <chris@1006.org>
Re: [pgsql-advocacy] Postgres and really huge tables Josh Berkus <josh@agliodbs.com>
Re: [pgsql-advocacy] Postgres and really huge tables "Luke Lonergan" <llonergan@greenplum.com>
Re: Postgres and really huge tables Tom Lane <tgl@sss.pgh.pa.us>
Re: [pgsql-advocacy] Postgres and really huge tables Oleg Bartunov <oleg@sai.msu.su>
Re: Postgres and really huge tables "Merlin Moncure" <mmoncure@gmail.com>
Re: Postgres and really huge tables Gavin Sherry <swm@alcove.com.au>
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.
В списке pgsql-performance по дате отправления
