Hi Melvin,
Thanks for this response. It still leave my question unanswered. I should rephrase it -- will <ltree> become a native datatype in Postgres (as opposed to remaining an extension). Are there any plans to make <ltree> a native datatype?
Michael
On Fri, Jun 12, 2015 at 7:58 AM, Melvin Davidson <melvin6925@xxxxxxxxx> wrote:
AFAIK, Most of the contributed modules have been changed into EXTENSIONsGeometric Data Types have been in PostgreSQL for quite a while.JSON have been in PostgreSQL since 9.2 and it's functionality increases with each new version.
http://www.postgresql.org/docs/9.2/interactive/datatype-geometric.html
http://www.postgresql.org/docs/9.2/interactive/datatype-json.htmlhttp://www.postgresql.org/docs/9.2/interactive/extend-extensions.html
http://www.postgresql.org/docs/9.2/interactive/external-extensions.htmlCheck the /share/contrib and /share/extension directories under the PostgreSQL main directory to see what is available for your version.--On Fri, Jun 12, 2015 at 8:22 AM, Michael Shapiro <mshapiro51@xxxxxxxxx> wrote:I am wondering if the contributed module <ltree> will always be part of Postgres? Do contributed modules ever get absorbed into Postgres itself?The reason I am asking is that, although ltree seems to have been a contributed module since at least 8.3, how can one know if it will always be part of subsequent versions of Postgres?Are there any plans to make <ltree> a built-in datatype, like <json>, o<xml>, or the various Geometric Types (eg, <polygon>)?Michael ShapiroSenior Systems EngineerNational Center for Supercomputing Applications (NCSA)University of Illinois, Urbana-Champaign (UIUC)Melvin Davidson
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.
