Re: Freeze avoidance of very large table.
От | Robert Haas |
---|---|
Тема | Re: Freeze avoidance of very large table. |
Дата | |
Msg-id | CA+TgmoZ8pGwXiXLY6y523_ea4e0ADL_RTo7tgH2Bcrbox3qhLA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Freeze avoidance of very large table. (Alvaro Herrera <alvherre@2ndquadrant.com>) |
Список | pgsql-hackers |
On Thu, Sep 3, 2015 at 2:26 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Robert Haas wrote: >> On Thu, Aug 20, 2015 at 10:46 AM, Alvaro Herrera >> <alvherre@2ndquadrant.com> wrote: > >> > I don't think that necessarily means it must continue to be in contrib. >> > Quite the contrary, I think it is a tool critical enough that it should >> > not be relegated to be a second-class citizen as it is now (let's face >> > it, being in contrib *is* second-class citizenship). >> >> I have resisted that principle for years and will continue to do so. >> It is entirely reasonable for some DBAs to want certain functionality >> (debugging tools, crypto) to not be installed on their machines. >> Folding everything into core is not a good policy, IMHO. > > I don't understand. I'm just proposing that the source code for the > extension to live in src/extensions/, and have the shared library > installed by toplevel make install; I'm not suggesting that the > extension is installed automatically. For that, you still need a > superuser to run CREATE EXTENSION. Oh. Well, that's different. I don't particularly support that proposal, but I'm not prepared to fight over it either. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: