File: load.l.html

package info (click to toggle)
mpsql 2.0-2
  • links: PTS
  • area: non-free
  • in suites: slink
  • size: 2,912 kB
  • ctags: 5,665
  • sloc: ansic: 34,322; makefile: 3,525; sh: 17
file content (58 lines) | stat: -rw-r--r-- 2,373 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
<!-- manual page source format generated by PolyglotMan v3.0.4, -->
<!-- available via anonymous ftp from ftp.cs.berkeley.edu:/ucb/people/phelps/tcltk/rman.tar.Z -->

<HTML>
<HEAD>
<TITLE>LOAD(SQL) manual page</TITLE>
</HEAD>
<BODY>
<A HREF="sql.html">SQL Reference Contents</A>
 
<H2><A NAME="sect0" HREF="#toc0">NAME </A></H2>
load - dynamically load an object file  
<H2><A NAME="sect1" HREF="#toc1">SYNOPSIS </A></H2>
<B>load </B> "filename" 
<BR>
  
<H2><A NAME="sect2" HREF="#toc2">DESCRIPTION </A></H2>
<B>Load</B> loads an object (or ".o") file into Postgres's address 
space.  Once a file is loaded, all functions in that file can be accessed. 
 This function is used in support of ADT's. <P>
If a file is not loaded using 
the  <B>load</B> command, the file will be loaded automatically the first time 
the function is called by Postgres. <B>Load</B> can also be used to reload an 
object file if it has been edited and recompiled.  Only objects created 
from C language files are supported at this time.  
<H2><A NAME="sect3" HREF="#toc3">EXAMPLE </A></H2>
-- <BR>
 --Load the file 
/usr/postgres/demo/circle.o <BR>
 -- <BR>
 load "/usr/postgres/demo/circle.o" <BR>
  
<H2><A NAME="sect4" HREF="#toc4">CAVEATS 
</A></H2>
Functions in loaded object files should not call functions in other object 
files loaded through the <B>load</B> command, meaning, for example, that all 
functions in file A should call each other, functions in the standard 
or math libraries, or in Postgres itself.  They should not call functions 
defined in a different loaded file B.  This is because if B is reloaded, 
the Postgres loader is not `smart' enough to relocate the calls from the 
functions in A into the new address space of B.  If B is not reloaded, 
however, there will not be a problem. <P>
On DECstations, you must use  <I>/bin/cc</I> 
with the `-G 0' option when compiling object files to be loaded. <P>
Note that 
if you are porting Postgres to a new platform, the <B>load</B> command will have 
to work in order to support ADTs. <P>

<HR><P>
<A NAME="toc"><B>Table of Contents</B></A><P>
<UL>
<LI><A NAME="toc0" HREF="#sect0">NAME</A></LI>
<LI><A NAME="toc1" HREF="#sect1">SYNOPSIS</A></LI>
<LI><A NAME="toc2" HREF="#sect2">DESCRIPTION</A></LI>
<LI><A NAME="toc3" HREF="#sect3">EXAMPLE</A></LI>
<LI><A NAME="toc4" HREF="#sect4">CAVEATS</A></LI>
</UL>
</BODY></HTML>