Re: [PERFORM] get/set priority of PostgreSQL backends

On Sat, Apr 7, 2012 at 11:05 AM, Scott Marlowe wrote: > On Sat, Apr 7, 2012 at 11:06 AM, Josh Kupershmidt wrote: >> The wiki says nice_backend_super() might be able to "renice any >> backend pid and set any priority, but is usable only by the [database] >> superuser", hinting that it would be fea

Re: [PERFORM] get/set priority of PostgreSQL backends

On Sat, Apr 7, 2012 at 11:06 AM, Josh Kupershmidt wrote: > The wiki says nice_backend_super() might be able to "renice any > backend pid and set any priority, but is usable only by the [database] > superuser", hinting that it would be feasible to lower a backend's > priority value (i.e. increase t

[PERFORM] get/set priority of PostgreSQL backends

Hi all, I noticed a note on the 'Priorities' wiki page[1], which talked about the need for having "a C-language function 'nice_backend(prio)' that renices the calling backend to "prio".', and suggests posting a link to this list. Well, here you go: http://pgxn.org/dist/prioritize/ The API is a

Re: [PERFORM] Planner selects slow "Bitmap Heap Scan" when "Index Scan" is faster

Hi all On Fri, Apr 6, 2012 at 19:11, Jeff Janes wrote: > On Wed, Apr 4, 2012 at 6:47 AM, Kim Hansen wrote: >> Hi All >> >> I have a query where the planner makes a wrong cost estimate, it looks >> like it underestimates the cost of a "Bitmap Heap Scan" compared to an >> "Index Scan". >> >> This