Re: [pgsql-advocacy] Increased company involvement
От | Tom Lane |
---|---|
Тема | Re: [pgsql-advocacy] Increased company involvement |
Дата | |
Msg-id | 25066.1115314079@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [pgsql-advocacy] Increased company involvement (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: [pgsql-advocacy] Increased company involvement
Re: [pgsql-advocacy] Increased company involvement |
Список | pgsql-hackers |
Josh Berkus <josh@agliodbs.com> writes: > Still sounds good. Do you think that this system could be extended to other > add-ons in the future which are currently more complex builds? And allow us > to out some of the wierder things in /contrib? The "system" already exists --- it's pgxs. We already have a report from Thomas Hallgren that pgxs works for building pljava, so I'm not too concerned about assuming it can be used for the other PLs. And I think we have already pgxs-ified all of contrib, though that's not the current standard method of building contrib. I have no problem with pushing out any part of contrib that doesn't seem tightly tied to the core server. I'm not entirely sure where to draw the line, but for instance I'd probably want to keep dblink where it is, since functions-returning-records are still in considerable flux. regards, tom lane
В списке pgsql-hackers по дате отправления: