From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Josh Berkus <josh(dot)berkus(at)pgexperts(dot)com> |
Cc: | postgres hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Why not install pgstattuple by default? |
Date: | 2011-05-06 08:06:55 |
Message-ID: | BANLkTinjRbn6bO5HMULerkhqGbsH_pSG1A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, May 6, 2011 at 00:34, Josh Berkus <josh(dot)berkus(at)pgexperts(dot)com> wrote:
> Hackers,
>
> I've run into a couple of occasions lately where I really wanted
> pgstattuple on a production server in order to check table/index bloat.
> However, in the production environment at a large site installing a
> contrib module can involve a process which takes days or weeks.
That can be said for a lot of things in contrib. pg_standby in 8.4 for
example. Or adminpack. Or dblink. Or hstore. There's a mix of "example
stuff" and "actually pretty darn useful in production stuff". I'm sure
you can find a couple of hundred emails in the archives on this very
topic.
From 9.1, it'll be a simple CREATE EXTENSION command - so much of the
problem goes away. Well. It doesn't go away, but it gets a lot more
neatly swept under the rug.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Tomasz Chmielewski | 2011-05-06 08:42:17 | Re: 'SGT DETAIL: Could not open file "pg_clog/05DC": No such file or directory' - what to do now? |
Previous Message | Teodor Sigaev | 2011-05-06 07:04:30 | Re: GSoC 2011: Fast GiST index build |