Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: RES: Priority to a mission critical transaction
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: carlos(dot)reimer(at)opendb(dot)com(dot)br
- Cc: "Jim C. Nasby" <jim(at)nasby(dot)net>, "Brad Nicholson" <bnichols(at)ca(dot)afilias(dot)info>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: RES: Priority to a mission critical transaction
- Date: Tue, 28 Nov 2006 14:07:05 -0500
"Carlos H. Reimer" <carlos(dot)reimer(at)opendb(dot)com(dot)br> writes: > There is an article about "Lowering the priority of a PostgreSQL query" > (http://weblog.bignerdranch.com/?p=11) that explains how to use the > setpriority() to lower PostgreSQL processes. > I?m wondering how much effective it would be for i/o bound systems. That article isn't worth the electrons it's written on. Aside from the I/O point, there's a little problem called "priority inversion". See the archives for (many) past discussions of nice'ing backends. regards, tom lane
- Follow-Ups:
- Re: RES: Priority to a mission critical transaction
- From: Bruce Momjian
- Re: RES: Priority to a mission critical transaction
- References:
- RES: Priority to a mission critical transaction
- From: Carlos H. Reimer
- RES: Priority to a mission critical transaction
- Prev by Date: RES: Priority to a mission critical transaction
- Next by Date: Re: RES: Priority to a mission critical transaction
- Previous by thread: RES: Priority to a mission critical transaction
- Next by thread: Re: RES: Priority to a mission critical transaction
- Indexes: