Re: actualized SQL/PSM patch

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, pgsql-patches <pgsql-patches(at)postgresql(dot)org>
Subject: Re: actualized SQL/PSM patch
Date: 2008-04-03 15:20:52
Message-ID: 200804031520.m33FKqB07912@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Andrew Dunstan wrote:
>
>
> Jonah H. Harris wrote:
> > On Tue, Apr 1, 2008 at 5:55 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> >
> >> The fundamental problem I've got with this patch is that it adds 400K
> >> of new code (and that's just the code, not counting documentation or
> >> regression tests) that we'll have to maintain, to obtain a feature that
> >> so far as I've heard there is precisely zero demand for.
> >>
> >
> > We have a customer that wants to use it as part of a MySQL-to-Postgres
> > migration.
> >
> >
>
> Using an implementation like this? I suspect anyone wanting to migrate
> their existing SQL/PSM stuff to Postgres will be less than impressed by
> our "function body as a string" mechanism.

What is your point? That because of the $$ strings they might as well
rewrite the whole thing in PL/pgSQL.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Bruce Momjian 2008-04-03 15:29:24 Re: actualized SQL/PSM patch
Previous Message Tom Lane 2008-04-03 15:18:20 Re: [PATCHES] Re: BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data