- first place.
- past that hurdle.]]>
+
tar> is required to unpack the source
+ distribution in the first place, in addition to either
+
+
+
+
+ The
zlib compression library will be
+ used by default. If you don't want to use it then you must
+ specify the option for
+ configure. Using this option disables
+ support for compressed archives in
pg_dump> and
+
+
+
- In the case of logfunc1, the
-
PostgreSQL main parser knows when
- preparing the plan for the INSERT, that the string
- 'now' should be interpreted as
- timestamp because the target column of logtable
- is of that type. Thus, it will make a constant from it at this
- time and this constant value is then used in all invocations of
- logfunc1 during the lifetime of the
- session. Needless to say that this isn't what the
- programmer wanted.
+ In the case of logfunc1, the
+
PostgreSQL main parser knows when
+ preparing the plan for the INSERT that the
+ string 'now' should be interpreted as
+ timestamp because the target column of
+ logtable is of that type. Thus,
+ 'now' will be converted to a constant when the
+ INSERT is planned, and then used in all
+ invocations of logfunc1 during the lifetime
+ of the session. Needless to say, this isn't what the programmer
+ wanted.
PL/pgSQL interpreter casts this
string to the timestamp type by calling the
text_out and timestamp_in
- functions for the conversion. So, the computed time stamp is updated
+ functions for the conversion. So, the computed timestamp is updated
on each execution as the programmer expects.
FOUND is a local variable within each
-
PL/pgSQL function;
so any changes
- to it affect only the current function.
+
PL/pgSQL function;
any changes to it
+ affect only the current function.
also means that a single prepared statement cannot be used by
multiple simultaneous database clients; however, each client can create
their own prepared statement to use. The prepared statement can be
- manually cleaned up using the DEALLOCATE> command.
+ manually cleaned up using the
+ endterm="sql-deallocate-title"> command.
Every function has a volatility> classification, with
the possibilities being VOLATILE>, STABLE>, or
IMMUTABLE>. VOLATILE> is the default if the
- <command>CREATE FUNCTION command does not specify a category.
- The volatility category is a promise to the optimizer about the behavior
- of the function:
+ <xref linkend="sql-createfunction" endterm="sql-createfunction-title">
+ command does not specify a category. The volatility category is a
+ promise to the optimizer about the behavior of the function:
file is retained in memory. Future calls in the same session to
the function(s) in that file will only incur the small overhead of
a symbol table lookup. If you need to force a reload of an object
- file, for example after recompiling it, use the LOAD>
- command or begin a fresh session.
+ file, for example after recompiling it, use the
+ linkend="sql-load" endterm="sql-load-title"> command or begin a
+ fresh session.
LANGUAGE C STRICT;
CREATE FUNCTION concat_text(text, text) RETURNS text
- AS 'DIRECTORY/funcs', 'concat_text',
+ AS 'DIRECTORY/funcs', 'concat_text'
LANGUAGE C STRICT;