From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Marko Kreen <markokr(at)gmail(dot)com> |
Cc: | Greg Smith <greg(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Why not install pgstattuple by default? |
Date: | 2011-05-18 19:37:32 |
Message-ID: | BANLkTikVMyyFtbTWC-2Q3B-apWxVOt=ifQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, May 18, 2011 at 15:29, Marko Kreen <markokr(at)gmail(dot)com> wrote:
> On Wed, May 18, 2011 at 2:57 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> On Wed, May 18, 2011 at 10:25, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:
>>> Some of my personal discussions of this topic have suggested that some other
>>> popular extensions like pgcrypto and hstore get converted too. I think
>>> those all fail test (3), and I'm not actually sure where pgcrypto adds any
>>> special dependency/distribution issues were it to be moved to the main
>>> database package. If this general idea catches on, a wider discussion of
>>> what else should get "promoted" to this extensions area would be
>>> appropriate. The ones I picked seemed the easiest to justify by this
>>> criteria set.
>>
>> pgcrypto would cause trouble for any builds *without* SSL. I don't
>> think any packagers do that, but people doing manual builds would
>> certainly get different results.
>
> What kind of trouble? It should work fine without SSL.
Oh, you're right - it does. But it does provide different
functionalties? Or does it actually do exactly the same stuff, just in
different ways?
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-05-18 20:54:25 | Re: Why not install pgstattuple by default? |
Previous Message | David E. Wheeler | 2011-05-18 19:36:04 | Re: deprecating contrib for PGXN |