From: "Dirk Lutzebaeck" <lutzeb@aeccom.com>
> It would be nice if a client could say: hey I know I have a large task
> / query please set me to a low priority. So the server would withdraw some
> cpu and io cycles from this task.
>
> On a per process basis one would do this with 'nice' but how could
> that be applied to the postmaster/postgres mechanism?
> Something like SET PRIORITY...
>
> Any comments?
Problem I can see is when you have interdependent transactions. If task A
takes longer to commit it could hold up everyone waiting on it.
On the other hand - I can see where you're coming from for large selects
(weekly summary reports - that sort of thing).
- Richard Huxton