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

From Bruce Momjian
Subject Re: actualized SQL/PSM patch
Date
Msg-id 200804031520.m33FKqB07912@momjian.us
Whole thread Raw
In response to Re: actualized SQL/PSM patch  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-patches
Andrew Dunstan wrote:
>
>
> 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.

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

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [BUGS] BUG #4070: Join more then ~15 tables let postgreSQL produces wrong data
Next
From: Bruce Momjian
Date:
Subject: Re: actualized SQL/PSM patch