Re: Postmaster hogs CPU - Mailing list pgsql-admin

From Gaetano Mendola
Subject Re: Postmaster hogs CPU
Date
Msg-id 40999B90.5080004@bigfoot.com
Whole thread Raw
In response to Re: Postmaster hogs CPU  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postmaster hogs CPU
List pgsql-admin
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Tom Lane wrote:

| Gaetano Mendola <mendola@bigfoot.com> writes:
|
|>You can basically renice the process that is performing the query.
|
|
| However, that's unlikely to do anything very pleasant, since you'll have
| priority-inversion problems.  "nice" has no idea when the process is
| holding a lock that someone else wants ...

That can be true, however in order to have a priority-inversion problem
I think are necessary 3 different level of priority, you have carefully
choose the postmaster and good value of nice in order to have it happen.

I was wandering about do the same work done with vacuum ( the sleep
trick each n records) in order to slow some expensive but not crucial
queries:

test> set query_delay = 10;  <-- 10 ms
test> select * from <very expensive query >;




Regards
Gaetano Mendola








-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (MingW32)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAmZuP7UpzwH2SGd4RAvVxAKCfvQDk2CkdcC2dCFtgg7nLzf7qTwCgt8/w
F0zVE0HYoI9lb9l7u9qwZIo=
=/mFq
-----END PGP SIGNATURE-----


pgsql-admin by date:

Previous
From: Tom Lane
Date:
Subject: Re: Postmaster hogs CPU
Next
From: Ludek Finstrle
Date:
Subject: Re: initdb: FATAL: conversion between LATIN2 and UNICODE