Re: [HACKERS] Re: [SQL] plpgsql error

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: Jan Wieck <jwieck(at)debis(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, brook(at)trillium(dot)NMSU(dot)Edu, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: [SQL] plpgsql error
Date: 1999-05-12 12:50:17
Message-ID: 199905121250.IAA18770@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> >
> > Brook Milligan <brook(at)trillium(dot)NMSU(dot)Edu> writes:
> > > Isn't the correct solution to have the Makefile contain a rule that
> > > creates the file from a template (e.g., with sed -e
> > > 's/@xxx@/${xxx}/g')? That way make resolves the variable references
> > > and you needn't worry about it.
> >
> > (after further thought...) Oh, right, I see what you're saying: don't
> > generate mklang.sql in configure at all, but let pl/plpgsql/src/Makefile
> > be responsible for it. Yeah, that'd be a cleaner solution. However,
> > what I just committed works ;-). If you feel like improving it, be
> > my guest; I have other items on the to-do list...
>
> I've just committed a little change to initdb and it's
> Makefile. The initdb Makefile now expands __DLSUFFIX__ into
> it and initdb uses $PGLIB/plpgsql__DLSUFFIX__ to test if it
> is there and then runs the appropriate queries against
> template1. Same for PL/Tcl.
>
> If anyone agrees we can get rid of these mklang.sql scripts
> totally.

Sure.

--
Bruce Momjian | http://www.op.net/~candle
maillist(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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-12 12:55:37 Update Open Items list
Previous Message Bruce Momjian 1999-05-12 12:47:53 Re: [HACKERS] misc and triggers regression tests failed on 6. 5be t a1