From: | Pavel Stehule <stehule(at)kix(dot)fsv(dot)cvut(dot)cz> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Denis Lussier <denis(at)enterprisedb(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Implementing SQL/PSM for PG 8.2 |
Date: | 2005-06-26 20:10:19 |
Message-ID: | Pine.LNX.4.44.0506262202330.27084-100000@kix.fsv.cvut.cz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, 26 Jun 2005, Tom Lane wrote:
> "Denis Lussier" <denis(at)enterprisedb(dot)com> writes:
> > For various technical and backward compatibility reasons, I don't think
> > SQL/PSM should be a replacement for PL/pgSQL. Although I do think it
> > should heavily leverage the solid foundation afforded by the PL/pgSQL
> > code base.
>
> "Solid"? I've wanted for quite some time to throw away plpgsql and
> start over --- there are too many things that need rewritten in it,
> starting with the parser. This project would be a great place to do
> that.
What is wrong on plpgsql code? I see some problems with processing SQL
statements, with efectivity evaluation of expr, but parser is clean (in my
opinion).
what have to be rewriten?
Regards
Pavel Stehule
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2005-06-26 20:31:51 | Re: language handlers in public schema? |
Previous Message | Tom Lane | 2005-06-26 19:55:18 | Re: language handlers in public schema? |