On 2013-08-29 15:07:35 -0400, Robert Haas wrote:
> On Thu, Aug 29, 2013 at 1:42 PM, Stephen Frost <sfr...@snowman.net> wrote:
> > To be honest, I don't find the arguments of "pgAdmin does it badly"
> > nor "psql users want this ability" (which I find difficult to believe)
> > to be particularlly compelling reasons to have a dangerous
> > implementation (even if it's better than 'adminpack' today) in core.
> I don't understand how you can find that difficult to believe.  I'm a
> psql user and I want it.  Josh Berkus is a psql user and he wants it.
> And there are numerous statements of support on these threads from
> other people as well.  The sheer volume of discussion on this topic,
> and the fact that it has not gone away after years of wrangling, is a
> clear indication that people do, in fact, want it.
> To be honest, I think the argument that this is dangerous is pretty
> ridiculous.


> > If it's in core rather than in contrib it's going to be deployed a great
> > deal farther with a large increase in userbase.  I've already stated
> > that if this is in contrib that my concerns are much less.
> I don't really see a compelling reason why it can't or shouldn't be in
> core.  But having something better in contrib would still be an
> improvement on the status quo.

I don't see much argument for putting it into contrib. One class of
users this will benefit is relatively new ones, possibly using some
GUI. Adding some additional complexity for them to enable the feature
seems pointless to me.

If you don't want your installation to use it, tell you ops people not
to do so. They are superusers, they need to have the ability to follow
some rules you make up internally.

The energy wasted in a good part of this massive 550+ messages thread is
truly saddening. We all (c|sh)ould have spent that time making PG more
awesome instead.


Andres Freund

 Andres Freund                     http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:

Reply via email to