It depends what the intended purpose if for. In our scenario, there are a number of ad-hoc export tasks running during the day that are quite cpu intensive.
There is a noticeably slow response time when exports are being run. By lowering the priority of the export postmaster, the system appeared to run far smoother for standard users.
I guess you could set-up a replication database which I probably will do in the end, however I just wanted to have a play and see if I could extend postgres with c. I don't profess to being a c or os guru. Thankyou for your feedback.
Theo
-----Original Message-----
From: Tom Lane [mailto:[EMAIL PROTECTED]]
Sent: Friday, 18 March 2005 11:06 AM
To: Theo Galanakis
Cc: pgsql-sql@postgresql.org
Subject: Re: [SQL] Process priority.
Theo Galanakis <[EMAIL PROTECTED]> writes:
> I wrote a C program that can be called through postgres via stored
> procedures. It allows you to change the current postmaster process
> priority.
You are aware that that's widely considered either useless or counterproductive? Renice-ing one backend seldom gives helpful results, because (a) what usually matters more than CPU usage is I/O, and renice doesn't change I/O priorities; (b) priority inversion results in higher-priority backends blocking behind the low-priority one whenever it's managed to acquire a lock.
regards, tom lane
| ______________________________________________________________________ This email, including attachments, is intended only for the addressee and may be confidential, privileged and subject to copyright. If you have received this email in error, please advise the sender and delete it. If you are not the intended recipient of this email, you must not use, copy or disclose its content to anyone. You must not copy or communicate to others content that is confidential or subject to copyright, unless you have the consent of the content owner. |
