pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
plpgsql error
12+ messages / 7 participants
[nested] [flat]

* plpgsql error
@ 1999-05-10 20:32  Adam H. Pendleton <apendleton@vgsinc.com>
  0 siblings, 1 reply; 12+ messages in thread

From: Adam H. Pendleton @ 1999-05-10 20:32 UTC (permalink / raw)
  To: pgsql-sql@hub.org

I get this error when I try to create a function using plpgsql:

ERROR:  Unrecognized language specified in a CREATE FUNCTION: 'plpgsql'.
Recognized languages are sql, C, internal and the created procedural
languages.

Do I need to specify another flag when I compile Postgresql?

Adam
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Si hoc legere scis nimium eruditionis habes.





^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* RE: [SQL] plpgsql error
@ 1999-05-10 20:46  Michael J Davis <michael.j.davis@tvguide.com>
  0 siblings, 1 reply; 12+ messages in thread

From: Michael J Davis @ 1999-05-10 20:46 UTC (permalink / raw)
  To: 'Adam H. Pendleton' <apendleton@vgsinc.com>; pgsql-sql@hub.org

Look in the docs for create language.  You need to execute a create language
command to tell postgres to recognize plpgsql.  I believe the library is
created as part of the install process.

> -----Original Message-----
> From:	Adam H. Pendleton [SMTP:apendleton@vgsinc.com]
> Sent:	Monday, May 10, 1999 2:32 PM
> To:	pgsql-sql@hub.org
> Subject:	[SQL] plpgsql error
> 
> I get this error when I try to create a function using plpgsql:
> 
> ERROR:  Unrecognized language specified in a CREATE FUNCTION: 'plpgsql'.
> Recognized languages are sql, C, internal and the created procedural
> languages.
> 
> Do I need to specify another flag when I compile Postgresql?
> 
> Adam
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Si hoc legere scis nimium eruditionis habes.
> 
> 



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-10 21:05  Andy Lewis <alewis@themecca.net>
  parent: Adam H. Pendleton <apendleton@vgsinc.com>
  0 siblings, 2 replies; 12+ messages in thread

From: Andy Lewis @ 1999-05-10 21:05 UTC (permalink / raw)
  To: Adam H. Pendleton <apendleton@vgsinc.com>; +Cc: pgsql-sql@hub.org

Edit: /usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql

Change: as '${exec_prefix}/lib/plpgsql.so'
to: as '/usr/local/pgsql/lib/plpgsql.so'

Then: psql your_db < mklang.sql

This should really be part of the documentation as I wasted two days on
this same problem a few weeks back.

Have fun

Andy

On Mon, 10 May 1999, Adam H. Pendleton wrote:

> I get this error when I try to create a function using plpgsql:
> 
> ERROR:  Unrecognized language specified in a CREATE FUNCTION: 'plpgsql'.
> Recognized languages are sql, C, internal and the created procedural
> languages.
> 
> Do I need to specify another flag when I compile Postgresql?
> 
> Adam
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Si hoc legere scis nimium eruditionis habes.
> 
> 
> 






^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-10 21:34  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Michael J Davis <michael.j.davis@tvguide.com>
  0 siblings, 0 replies; 12+ messages in thread

From: Tom Lane @ 1999-05-10 21:34 UTC (permalink / raw)
  To: Michael J Davis <michael.j.davis@tvguide.com>; +Cc: 'Adam H. Pendleton' <apendleton@vgsinc.com>; pgsql-sql@hub.org

Michael J Davis <michael.j.davis@tvguide.com> writes:
> Look in the docs for create language.  You need to execute a create language
> command to tell postgres to recognize plpgsql.  I believe the library is
> created as part of the install process.

plpgsql isn't installed into the system by default; you have to do the
appropriate incantation after installing and starting the base Postgres
system.  ISTR there is a shell script you should run to do all that's
needful --- look in the plpgsql docs and/or source files.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-10 21:38  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Andy Lewis <alewis@themecca.net>
  1 sibling, 0 replies; 12+ messages in thread

From: Bruce Momjian @ 1999-05-10 21:38 UTC (permalink / raw)
  To: Andy Lewis <alewis@themecca.net>; +Cc: Adam H. Pendleton <apendleton@vgsinc.com>; PostgreSQL-development <hackers@postgreSQL.org>


Yes, this clearly looks broken.  In mklang.sql.in, @libdir@ is replaced
with ${exec_prefix} in mklang.sql.  Seems it should be something else.


> Edit: /usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql
> 
> Change: as '${exec_prefix}/lib/plpgsql.so'
> to: as '/usr/local/pgsql/lib/plpgsql.so'
> 
> Then: psql your_db < mklang.sql
> 
> This should really be part of the documentation as I wasted two days on
> this same problem a few weeks back.
> 
> Have fun
> 
> Andy
> 
> On Mon, 10 May 1999, Adam H. Pendleton wrote:
> 
> > I get this error when I try to create a function using plpgsql:
> > 
> > ERROR:  Unrecognized language specified in a CREATE FUNCTION: 'plpgsql'.
> > Recognized languages are sql, C, internal and the created procedural
> > languages.
> > 
> > Do I need to specify another flag when I compile Postgresql?
> > 
> > Adam
> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > Si hoc legere scis nimium eruditionis habes.
> > 
> > 
> > 
> 
> 
> 
> 
> 


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



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-11 07:35  Jan Wieck <jwieck@debis.com>
  parent: Andy Lewis <alewis@themecca.net>
  1 sibling, 2 replies; 12+ messages in thread

From: jwieck@debis.com @ 1999-05-11 07:35 UTC (permalink / raw)
  To: alewis@themecca.net; +Cc: apendleton@vgsinc.com; pgsql-sql@hub.org

>
> Edit: /usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql
>
> Change: as '${exec_prefix}/lib/plpgsql.so'
> to: as '/usr/local/pgsql/lib/plpgsql.so'
>
> Then: psql your_db < mklang.sql
>
> This should really be part of the documentation as I wasted two days on
> this same problem a few weeks back.

    And this became IMHO an FAQ. Should we avoid it by installing
    PL/pgSQL and PL/Tcl (if built) by default  in  the  template1
    database  during  intidb?   Installing  it in template1 would
    have the  effect  that  it  will  be  available  after  every
    createdb.


Jan

--

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





^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* RE: [SQL] plpgsql error
@ 1999-05-11 14:23  Michael J Davis <michael.j.davis@tvguide.com>
  0 siblings, 1 reply; 12+ messages in thread

From: Michael J Davis @ 1999-05-11 14:23 UTC (permalink / raw)
  To: 'jwieck@debis.com' <jwieck@debis.com>; alewis@themecca.net; +Cc: apendleton@vgsinc.com; pgsql-sql@hub.org

Gets my vote.  Should we also consider doing this for Perl too?  I turn them
all on in my installation.  I don't use either Perl or TCL yet but want to
make sure they are available if 1) I ever want to or 2) a need arises that
is would be better suited to either Perl or TCL.

Thanks, Michael D.

	-----Original Message-----
	From:	jwieck@debis.com [SMTP:jwieck@debis.com]
	Sent:	Tuesday, May 11, 1999 1:35 AM
	To:	alewis@themecca.net
	Cc:	apendleton@vgsinc.com; pgsql-sql@hub.org
	Subject:	Re: [SQL] plpgsql error

	>
	> Edit:
/usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql
	>
	> Change: as '${exec_prefix}/lib/plpgsql.so'
	> to: as '/usr/local/pgsql/lib/plpgsql.so'
	>
	> Then: psql your_db < mklang.sql
	>
	> This should really be part of the documentation as I wasted two
days on
	> this same problem a few weeks back.

	    And this became IMHO an FAQ. Should we avoid it by installing
	    PL/pgSQL and PL/Tcl (if built) by default  in  the  template1
	    database  during  intidb?   Installing  it in template1 would
	    have the  effect  that  it  will  be  available  after  every
	    createdb.


	Jan

	--

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

	



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-11 14:27  Jan Wieck <jwieck@debis.com>
  parent: Michael J Davis <michael.j.davis@tvguide.com>
  0 siblings, 0 replies; 12+ messages in thread

From: jwieck@debis.com @ 1999-05-11 14:27 UTC (permalink / raw)
  To: michael.j.davis@tvguide.com; +Cc: jwieck@debis.com; alewis@themecca.net; apendleton@vgsinc.com; pgsql-sql@hub.org

Michael J Davis wrote:

>
> Gets my vote.  Should we also consider doing this for Perl too?  I turn them
> all on in my installation.  I don't use either Perl or TCL yet but want to
> make sure they are available if 1) I ever want to or 2) a need arises that
> is would be better suited to either Perl or TCL.
>
>        And this became IMHO an FAQ. Should we avoid it by installing
>        PL/pgSQL and PL/Tcl (if built) by default  in  the  template1
>        database  during  intidb?   Installing  it in template1 would
>        have the  effect  that  it  will  be  available  after  every
>        createdb.

    I  only  spoke about installing the procedural languages that
    got built (due to the config options used) by default in  the
    template1  database.  NOT  to  turn  on the config options by
    default.


Jan

--

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





^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-11 14:28  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Jan Wieck <jwieck@debis.com>
  1 sibling, 0 replies; 12+ messages in thread

From: Tom Lane @ 1999-05-11 14:28 UTC (permalink / raw)
  To: jwieck@debis.com; +Cc: alewis@themecca.net; apendleton@vgsinc.com; pgsql-sql@hub.org

jwieck@debis.com (Jan Wieck) writes:
>> Change: as '${exec_prefix}/lib/plpgsql.so'
>> to: as '/usr/local/pgsql/lib/plpgsql.so'
>> 
>> This should really be part of the documentation as I wasted two days on
>> this same problem a few weeks back.

>     And this became IMHO an FAQ. Should we avoid it by installing
>     PL/pgSQL and PL/Tcl (if built) by default  in  the  template1
>     database  during  intidb?

Actually, I thought the same until last night, when I realized that
mklang.sql is in fact being made wrong --- the ${exec_prefix} should
be expanded when the file is created, but it isn't.  (There's another
bug in it too: .so is hardwired, when it should be DLSUFFIX.)

So now I think what's really going on is that people *are* faithfully
following the install directions, but it's not working because of this
screwup.  Oops.

Fixing it is not quite as trivial as I first thought --- see related
messages in hackers list.

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-11 14:56  Bruce Momjian <maillist@candle.pha.pa.us>
  parent: Jan Wieck <jwieck@debis.com>
  1 sibling, 0 replies; 12+ messages in thread

From: Bruce Momjian @ 1999-05-11 14:56 UTC (permalink / raw)
  To: Jan Wieck <jwieck@debis.com>; +Cc: Andy Lewis <alewis@themecca.net>; apendleton@vgsinc.com; pgsql-sql@hub.org

> >
> > Edit: /usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql
> >
> > Change: as '${exec_prefix}/lib/plpgsql.so'
> > to: as '/usr/local/pgsql/lib/plpgsql.so'
> >
> > Then: psql your_db < mklang.sql
> >
> > This should really be part of the documentation as I wasted two days on
> > this same problem a few weeks back.
> 
>     And this became IMHO an FAQ. Should we avoid it by installing
>     PL/pgSQL and PL/Tcl (if built) by default  in  the  template1
>     database  during  intidb?   Installing  it in template1 would
>     have the  effect  that  it  will  be  available  after  every
>     createdb.

Sure, why not?


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



^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* RE: [SQL] plpgsql error
@ 1999-05-11 17:25  Dr. Nisai Wanakule <nisai@m1p17-235.waterauthority.state.fl.us>
  0 siblings, 1 reply; 12+ messages in thread

From: Dr. Nisai Wanakule @ 1999-05-11 17:25 UTC (permalink / raw)
  To: pgsql-sql@hub.org; +Cc: michael.j.davis@tvguide.com

What version that has Procedural Language support for Perl?

>X-Authentication-Warning: hub.org: majordom set sender to 
owner-pgsql-sql@postgreSQL.org using -f
>From: Michael J Davis <michael.j.davis@tvguide.com>
>To: "'jwieck@debis.com'" <jwieck@debis.com>, alewis@themecca.net
>Cc: apendleton@vgsinc.com, pgsql-sql@hub.org
>Subject: RE: [SQL] plpgsql error
>Date: Tue, 11 May 1999 09:23:32 -0500
>MIME-Version: 1.0
>
>Gets my vote.  Should we also consider doing this for Perl too?  I turn them
>all on in my installation.  I don't use either Perl or TCL yet but want to
>make sure they are available if 1) I ever want to or 2) a need arises that
>is would be better suited to either Perl or TCL.
>
>Thanks, Michael D.
>
>	-----Original Message-----
>	From:	jwieck@debis.com [SMTP:jwieck@debis.com]
>	Sent:	Tuesday, May 11, 1999 1:35 AM
>	To:	alewis@themecca.net
>	Cc:	apendleton@vgsinc.com; pgsql-sql@hub.org
>	Subject:	Re: [SQL] plpgsql error
>
>	>
>	> Edit:
>/usr/src/pgsql/postgresql-6.4.2/src/pl/plpgsql/src/mklang.sql
>	>
>	> Change: as '${exec_prefix}/lib/plpgsql.so'
>	> to: as '/usr/local/pgsql/lib/plpgsql.so'
>	>
>	> Then: psql your_db < mklang.sql
>	>
>	> This should really be part of the documentation as I wasted two
>days on
>	> this same problem a few weeks back.
>
>	    And this became IMHO an FAQ. Should we avoid it by installing
>	    PL/pgSQL and PL/Tcl (if built) by default  in  the  template1
>	    database  during  intidb?   Installing  it in template1 would
>	    have the  effect  that  it  will  be  available  after  every
>	    createdb.
>
>
>	Jan
>
>	--
>
>	
>#======================================================================#
>	# It's easier to get forgiveness for being wrong than for being
>right. #
>	# Let's break this rule - forgive me.
>#
>	#======================================== jwieck@debis.com (Jan
>Wieck) #
>
>	
>


--
Nisai Wanakule, PH.D., P.E.
Tampa Bay Water
2535 Landmark Dr., Suite 211
Clearwater, FL 33761
Tel 727/791-2373
Fax 727/791-2388
SunCom: 513-7010




^ permalink  raw  reply  [nested|flat] 12+ messages in thread

* Re: [SQL] plpgsql error
@ 1999-05-11 17:45  Jan Wieck <jwieck@debis.com>
  parent: Dr. Nisai Wanakule <nisai@m1p17-235.waterauthority.state.fl.us>
  0 siblings, 0 replies; 12+ messages in thread

From: jwieck@debis.com @ 1999-05-11 17:45 UTC (permalink / raw)
  To: nisai@m1p17-235.waterauthority.state.fl.us; +Cc: pgsql-sql@hub.org; michael.j.davis@tvguide.com

Nisai Wanakule wrote:

>
> What version that has Procedural Language support for Perl?
>

    None  -  there is only client access support for Perl so far.
    I'm still waiting for a Perl guru who has the  knowledge  how
    to integrate a Perl interpreter into another program.

    I've implemented the CREATE LANGUAGE and changed the function
    manager to recognize functions in procedural  languages.  And
    I've  written  PL/Tcl  and PL/pgSQL, so I can (and am willing
    to) answer all questions about how to interface  from  a  new
    language  module to fmgr or SPI. But I'm not willing to learn
    Perl, Python etc. plus their API just  to  create  all  these
    PL's.


Jan

--

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





^ permalink  raw  reply  [nested|flat] 12+ messages in thread


end of thread, other threads:[~1999-05-11 17:45 UTC | newest]

Thread overview: 12+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-05-10 20:32 plpgsql error Adam H. Pendleton <apendleton@vgsinc.com>
1999-05-10 21:05 ` Andy Lewis <alewis@themecca.net>
1999-05-10 21:38   ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-05-11 07:35   ` Jan Wieck <jwieck@debis.com>
1999-05-11 14:28     ` Tom Lane <tgl@sss.pgh.pa.us>
1999-05-11 14:56     ` Bruce Momjian <maillist@candle.pha.pa.us>
1999-05-10 20:46 RE: [SQL] plpgsql error Michael J Davis <michael.j.davis@tvguide.com>
1999-05-10 21:34 ` Tom Lane <tgl@sss.pgh.pa.us>
1999-05-11 14:23 RE: [SQL] plpgsql error Michael J Davis <michael.j.davis@tvguide.com>
1999-05-11 14:27 ` Jan Wieck <jwieck@debis.com>
1999-05-11 17:25 RE: [SQL] plpgsql error Dr. Nisai Wanakule <nisai@m1p17-235.waterauthority.state.fl.us>
1999-05-11 17:45 ` Jan Wieck <jwieck@debis.com>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox