From 52ca2ab26852caf5715f92fa8457eaad4be5e9cc Mon Sep 17 00:00:00 2001 From: "Thomas G. Lockhart" Date: Tue, 22 Sep 1998 15:48:03 +0000 Subject: Editing and markup cleanup. --- doc/src/sgml/ref/create_language.sgml | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) (limited to 'doc/src/sgml/ref/create_language.sgml') diff --git a/doc/src/sgml/ref/create_language.sgml b/doc/src/sgml/ref/create_language.sgml index 73e409c42ab..5b2bbaa5a45 100644 --- a/doc/src/sgml/ref/create_language.sgml +++ b/doc/src/sgml/ref/create_language.sgml @@ -40,9 +40,10 @@ CREATE [ TRUSTED ] PROCEDURAL LANGUAGE 'langname< TRUSTED specifies that the call handler for the language is safe; that is, it offers an unprivileged user - no functionality to get around access restrictions. If + no functionality to bypass access restrictions. If this keyword is omitted when registering the language, - only users with the PostgreSQL superuser privilege can use + only users with the Postgres +superuser privilege can use this language to create new functions (like the 'C' language). @@ -58,17 +59,17 @@ CREATE [ TRUSTED ] PROCEDURAL LANGUAGE 'langname< The name of the new procedural language. The language name is case insensitive. A procedural language cannot override one of the built-in languages of - PostgreSQL. + Postgres. - call_handler + HANDLER call_handler - The argument for HANDLER is the name + call_handler is the name of a previously registered function that will be called to execute the PL procedures. @@ -86,7 +87,7 @@ CREATE [ TRUSTED ] PROCEDURAL LANGUAGE 'langname< inserted in the LANCOMPILER attribute of the new pg_language entry. At present, - PostgreSQL doesn't use + Postgres does not use this attribute in any way. @@ -364,7 +365,8 @@ CREATE PROCEDURAL LANGUAGE 'plsample' SQL92 - There is no CREATE LANGUAGE statement in SQL92. + There is no CREATE LANGUAGE statement in + SQL92. -- cgit v1.2.3