| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | "Kris Kennaway" <kris(at)obsecurity(dot)org> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Maxime Henrion" <mux(at)freebsd(dot)org>, <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [mux@FreeBSD.org: Re: Anyone interested in improving postgresql scaling?] |
| Date: | 2007-04-11 12:41:05 |
| Message-ID: | 878xcz13tq.fsf@oxford.xeocode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Kris Kennaway" <kris(at)obsecurity(dot)org> writes:
> If there really are users who find 10 proctitle updates/second an
> unacceptably low update rate, then tune for the default case and
> provide an option to allow them to override the rate limit to whatever
> update rate they find appropriate.
If you rate limit the naive way you would end up with info that's arbitrarily
old and out of date. To get something that's guaranteed not to be older than
some maximum age we would have to start with setting timers and setting the
proctitle in a signal handler which would be much more complex than what I
think you're imagining.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-04-11 12:57:12 | Re: Question about SHM_QUEUE |
| Previous Message | Peter Eisentraut | 2007-04-11 12:27:47 | UUID generation functions |