Re: PostgreSQLs Extension

Hi!
Thanks for quick response.
> you can create new data types, new operators, new types of indexes if
> you want... the question is, what are you trying to do?
I want to define a new type of geographic data, as well as the PostGIS's data. Also, my intention is to define new topological operators (eg intersection). For this, I wonder if using the approach of User-Defined Types is best. With this approach can I change the query processing to handle the new type the way I want? This approach directly affects the performance in query processing?

> what kind of changes?

Also, maybe I'll make changes to the SQL language and implement them in PostgreSQL. Per example, changes in syntax and define new reserved words (for any specific treatment, when it detected my data type).
Thanks for help.
Best regards,
Anderson Carniel[]s
> From: jaime(at)2ndquadrant(dot)com
> Date: Fri, 27 Jul 2012 19:51:53 -0500
> Subject: Re: [HACKERS] PostgreSQLs Extension
> To: accarniel(at)gmail(dot)com
> CC: pgsql-hackers(at)postgresql(dot)org
>
> On Thu, Jul 26, 2012 at 2:56 PM, Anderson C. Carniel
> <accarniel(at)gmail(dot)com> wrote:
> >
> > -> I need to set a new data type specific, as the PostGIS. I saw that in
> > PostgreSQL's Documentation there is a User-Defined Types. This is the best
> > way to define a new data type? Using this approach, can I define the way
> > queries are processed and thus define new operators? Or would I define
> > functions via pgsql for this? It was not clear to me.
>
> you can create new data types, new operators, new types of indexes if
> you want... the question is, what are you trying to do?
>
> > -> Also, how could I make changes to the SQL language in PostgreSQL?
> >
>
> what kind of changes?
>
> --
> Jaime Casanova www.2ndQuadrant.com
> Professional PostgreSQL: Soporte 24x7 y capacitación