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

From: jwieck(at)debis(dot)com (Jan Wieck)
To: tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane)
Cc: brook(at)trillium(dot)NMSU(dot)Edu, hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Re: [SQL] plpgsql error
Date: 1999-05-12 10:37:24
Message-ID: m10hWOD-000EBaC@orion.SAPserv.Hamburg.dsh.de
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.

Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me. #
#======================================== jwieck(at)debis(dot)com (Jan Wieck) #

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mirko Kaffka 1999-05-12 10:48:29 backend dies suddenly after a lot of error messages
Previous Message Jan Wieck 1999-05-12 10:26:50 Re: [HACKERS] 6.5 TODO list