Re: Inline Extension
От | Tom Lane |
---|---|
Тема | Re: Inline Extension |
Дата | |
Msg-id | 3157.1327298440@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Inline Extension (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Inline Extension
|
Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes: > ... If people > are doing management via "pure FEBE", good for them: but that doesn't > explain why it shoudn't be done all in userspace, with all of the > flexibility that gives. On reflection it seems like this patch is simply offering the wrong solution for the problem. I agree that it could be useful to install extensions without having direct access to the server's filesystem, but it doesn't seem to follow that we must lobotomize existing extension features in order to have that. I pointed out earlier that you could get such functionality via contrib/adminpack, though people not unreasonably complained that that was pretty ugly and low-level. But couldn't we define some SQL-level operations to allow installing extension control and script files? Probably the worst issue with that is that in typical installations, the share/extension/ directory would be read-only to the server, and a lot of people might be uncomfortable with making it writable. Not sure whether we should consider inventing another place to keep SQL-command-installed extensions, or just say "if you want this functionality you have to make share/extension/ writable". regards, tom lane
В списке pgsql-hackers по дате отправления: