All,
> We might get somewhere by trying to identify a small set of particularly
> popular contrib modules that don't add any extra dependencies, and then
> recommending to packagers that those ones get bundled into the main
> server package.
Yeah, I wasn't thinking of including all of contrib. There's a lot of
reasons not to do that. I was asking about pgstattuple in particular,
since it's:
(a) small
(b) has no external dependancies
(c) adds no stability risk or performance overhead
(d) is usually needed on production systems when it's needed at all
It's possible that we have one or two other diagnostic utilities which
meet the above profile. pageinspect, maybe?
The reason why this is such an issue is that for big users with
high-demand production environments, installing any software, even
postgresql-devel or postgresql-contrib packages, are big major IT deals
which require weeks of advance scheduling. As a result, diagnostic
tools from contrib tend not to be used because the problem they need to
diagnose is much more urgent than that.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com