Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id TAA93162 for ; Mon, 10 Jan 2000 19:40:50 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id TAA07471; Mon, 10 Jan 2000 19:40:16 -0500 (EST) To: werner.fraga@computalog.com cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] problems creating functions and triggers In-reply-to: <00011015363303.07948@shorty.edmonton.computalog.com> References: <00011015363303.07948@shorty.edmonton.computalog.com> Comments: In-reply-to Werner Fraga message dated "Mon, 10 Jan 2000 15:32:19 -0700" Date: Mon, 10 Jan 2000 19:40:16 -0500 Message-ID: <7468.947551216@sss.pgh.pa.us> From: Tom Lane Werner Fraga writes: > 1. I noticed that some examples show the LANGUAGE in the CREATE FUNCTION > command can be 'plpgsql'. However, if I try using this instead of 'sql', I get > ERROR: Unrecognized language specified in a CREATE FUNCTION ... You need to run the "createlang" script to install plpgsql in the particular database you are using. If you want plpgsql to be available by default in a given installation, you can install it in template1 --- subsequently created DBs will be clones of template1. > 3. Is there anywhere I can find a list of the system tables? (that section in > Bruce's book is still empty...) \dS in psql... regards, tom lane