Branch :
| Author | Commit | Date | CI | Message |
|---|---|---|---|---|
| 3f680606 | 2013-03-11 02:52:04 | PERMIT_* / REGRESS->TEST sweep | ||
| 01d3f160 | 2012-07-10 12:08:29 | sync with top(1) in base; remove KERNBASE. ok okan@ | ||
| 88ea7291 | 2012-03-29 13:38:12 | Change SEPARATE_BUILD=(concurrent|simple) to Yes; bsd.port.mk doesn't make a distinction between these. ok aja@ dcoppa@ | ||
| 4b0fead1 | 2012-01-08 20:56:03 | catch up with change KERN_PROC2 -> KERN_PROC | ||
| 61199a1d | 2011-09-16 08:48:01 | normalize pkgpath | ||
| 2314c85f | 2010-11-15 00:22:45 | convert to new style depends zap default spec that are not needed convert libspecs as well convert p* to REVISION. No package changes | ||
| cd474773 | 2010-11-06 22:50:02 | bye bye old LIB_DEPENDS | ||
| 880de1aa | 2010-10-18 17:06:05 | USE_GROFF=Yes | ||
| fffff451 | 2008-06-10 20:48:10 | import pg_top pg_top is 'top' for PostgreSQL. It is derived from Unix Top. Similar to top, pg_top allows you to monitor PostgreSQL processes. It also allows you to: * View currently running SQL statement of a process. * View query plan of a currently running SELECT statement. * View locks held by a process. * View user table statistics. * View user index statistics man page suggestion from sthen - thanks! feedback and ok merdely |