Re: Coping with 'C' vs 'newC' function language names

So new-style C functions are language "newC"?

> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > I don't really have a better idea, but consider if you installed 7.1 into
> > /opt/postgres71: then this dump will load the old version of plpgsql.sl.
>
> True, but absolute paths in a dump file are a different (and
> long-standing) issue.
>
> > Assuming that that would work in the first place, LANGUAGE 'C' is correct.
>
> It wouldn't work, so that's irrelevant. The PL handlers know way more
> than the average user-defined function about backend innards, and aren't
> usually cross-version compatible. They won't be this time, for sure.
>
> > Btw., could we use something other than 'newC'? It's going to get old
> > really fast (pun intended). Maybe 'Cv2' or something along these lines?
>
> Where were you six months ago? ;-( It's a bit late in the dev cycle to
> be running around renaming this kind of stuff...
>
> regards, tom lane
>

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026