Re: [HACKERS] PostgreSQL future ideas - Mailing list pgsql-general

From postgres Emanuel CALVO FRANCO
Subject Re: [HACKERS] PostgreSQL future ideas
Date
Msg-id f205bb120809291427q506f22e7oe8f9ddb9e16c3fef@mail.gmail.com
Whole thread Raw
List pgsql-general
2008/9/27 Douglas McNaught <doug@mcnaught.org>:
> On Sat, Sep 27, 2008 at 12:13 PM, Mark Mielke <mark@mark.mielke.cc> wrote:
>> If
>> some parts of PostgreSQL are not performance bottlenecks, and they are
>> extremely complicated to write in C, and very easy to write in something
>> else common and simple (I've never used LUA myself?), I imagine it would be
>> acceptable to the community.
>
> As long as they can expose their interfaces using the standard PG
> function call interface, and use the documented SPI mechanism to talk
> to the rest of the back end.  Stuff that hooks into undocumented or
> unstable parts of the code would be much less viable.
>
> -Doug
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>

I think that C is the best language for Postgresql. C++ has a little
thinks that make not good for performance.
Why people want to make more understable code touching the language?.
Simplify documentation for programmmers. Thats was the idea in the beggining.

pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Counting unique rows as an aggregate.
Next
From: Greg Smith
Date:
Subject: Re: pg_start_backup() takes too long