Re: actualized SQL/PSM patch - Mailing list pgsql-patches

From Andrew Dunstan
Subject Re: actualized SQL/PSM patch
Date
Msg-id 47F45E6E.1050706@dunslane.net
Whole thread Raw
In response to Re: actualized SQL/PSM patch  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Responses Re: actualized SQL/PSM patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: actualized SQL/PSM patch  (Bruce Momjian <bruce@momjian.us>)
List pgsql-patches

Jonah H. Harris wrote:
> On Tue, Apr 1, 2008 at 5:55 PM, Tom Lane <tgl@sss.pgh.pa.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.

cheers

andrew

pgsql-patches by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: actualized SQL/PSM patch
Next
From: Tom Lane
Date:
Subject: Re: actualized SQL/PSM patch