Re: Any reasons to not move pgstattuple to core? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Any reasons to not move pgstattuple to core?
Date
Msg-id 20131004013620.GV5235@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: Any reasons to not move pgstattuple to core?  (Sergey Konoplev <gray.ru@gmail.com>)
Responses Re: Any reasons to not move pgstattuple to core?  (Peter Geoghegan <pg@heroku.com>)
List pgsql-hackers
Sergey Konoplev escribió:
> On Thu, Oct 3, 2013 at 3:55 PM, Peter Geoghegan <pg@heroku.com> wrote:
> > On Thu, Oct 3, 2013 at 3:34 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> >> Well, this is a general problem with any extension - somebody might
> >> want it on a system on which the admin is unable or unwilling to
> >> install it.  But we can't put every possible extension in core.
> >
> > The flip-side is that we could have made an awful lot of built-in
> > things extensions, but for whatever reason chose not to. I'm not
> > necessarily in favor of putting pgstattuple in core, but the question
> > should be asked: Why should we do this here? In what way is
> > pgstattuple like or not like the other things that are in core?
> 
> I would highlight it as it became a kind of routine one. Also,
> sometimes it is required to solve problems, not to make new features,
> so it often can not wait.

Greg Smith made a list some months ago of contrib modules that were
essential for forensics analysis and such.  Weren't we going to do
something special about those?

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: record identical operator
Next
From: Peter Geoghegan
Date:
Subject: Re: Any reasons to not move pgstattuple to core?