From: | Tobias Brox <tobias(at)nordicbet(dot)com> |
---|---|
To: | Tobias Brox <tobias(at)nordicbet(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: "nice"/low priority Query |
Date: | 2005-08-02 19:59:15 |
Message-ID: | 20050802195915.GA9691@tobias.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
[Tobias Brox - Tue at 06:04:34PM +0200]
> (...) and at one
> point in the code I'm even asking the database for "explain plan", grepping
> out the estimated cost number, and referring the user to take contact with
> the IT-dept if he really needs the report. But I digress.
I just came to think about some more "dirty" tricks I can do. I have turned
on stats collection in the configuration; now, if I do:
select count(*) from pg_stat_activity where not current_query like '<IDLE>%';
or, eventually:
select count(*) from pg_stat_activity
where not current_query like '<IDLE>%' and query_start+'1 second'<now();
it will give a hint about how busy the database server is, thus I can
eventually let the application sleep and retry if there are any other heavy
queries in progress.
--
Tobias Brox, +47-91700050
Nordicbet, IT dept
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Huxton | 2005-08-03 08:53:29 | Re: "nice"/low priority Query |
Previous Message | Sailer, Denis (YBUSA-CDR) | 2005-08-02 18:57:50 | pg_dump for table with bytea takes a long time |