<!--

$PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.30 2005/10/1515:29:24 momjian Exp $

$PostgreSQL: pgsql/doc/src/sgml/config.sgml,v 1.31 2005/10/1520:12:32 neilc Exp $

-->

<chapter Id="runtime-config">

<title>Run-time Configuration</title>

Each recognized escape is replaced as outlined

below - anything else that looks like an escape is ignored. Other

characters are copied straight to the log line. Some escapes are

onlyrecognised by session processes, and do not apply to

onlyrecognized by session processes, and do not apply to

background processes such as the postmaster. <application>Syslog</>

produces its own

time stamp and process ID information, so you probably do not want to

<!-- $PostgreSQL: pgsql/doc/src/sgml/information_schema.sgml,v 1.21 2005/08/27 14:13:21 momjian Exp $ -->

<!-- $PostgreSQL: pgsql/doc/src/sgml/information_schema.sgml,v 1.22 2005/10/15 20:12:32 neilc Exp $ -->

<chapter id="information-schema">

<title>The Information Schema</title>

</row>

<row>

<entry><literal>sql_language_comformance</literal></entry>

<entry><literal>sql_language_conformance</literal></entry>

<entry><type>character_data</type></entry>

<entry>

The standard conformance level for the language binding. For

<!--

$PostgreSQL: pgsql/doc/src/sgml/planstats.sgml,v 1.3 2005/03/14 06:49:48 neilc Exp $

$PostgreSQL: pgsql/doc/src/sgml/planstats.sgml,v 1.4 2005/10/15 20:12:32 neilc Exp $

-->

<chapter id="planner-stats-details">

<para>

The outputs and algorithms shown below are taken from version 8.0.

Thebehaviour of earlier (or later) versions may vary.

Thebehavior of earlier (or later) versions may vary.

</para>

<sect1 id="row-estimation-examples">

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.11 2005/09/13 15:24:57 neilc Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/alter_sequence.sgml,v 1.12 2005/10/15 20:12:33 neilc Exp $

PostgreSQL documentation

-->

specified, any calls to <function>nextval</function> after the

sequence has reached its maximum value will return an error.

If neither <literal>CYCLE</literal> or <literal>NO

CYCLE</literal> are specified, the old cyclebehaviour will be

CYCLE</literal> are specified, the old cyclebehavior will be

maintained.

</para>

</listitem>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.69 2005/10/13 14:44:58 momjian Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/copy.sgml,v 1.70 2005/10/15 20:12:33 neilc Exp $

PostgreSQL documentation

-->

Separated Value (<literal>CSV</>) file format used by many other

programs, such as spreadsheets. Instead of the escaping used by

<productname>PostgreSQL</productname>'s standard text mode, it

produces andrecognises the common CSV escaping mechanism.

produces andrecognizes the common CSV escaping mechanism.

</para>

<para>

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.29 2005/01/09 05:57:45 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/create_table_as.sgml,v 1.30 2005/10/15 20:12:33 neilc Exp $

PostgreSQL documentation

-->

<para>

Prior to <productname>PostgreSQL</productname> 8.0, <command>CREATE

TABLE AS</command> always included OIDs in the table it

produced. As of <productname>PostgresSQL</productname> 8.0,

produced. As of <productname>PostgreSQL</productname> 8.0,

the <command>CREATE TABLE AS</command> command allows the user to

explicitly specify whether OIDs should be included. If the

presence of OIDs is not explicitly specified,

<!--

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.53 2005/10/10 22:29:47 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/ref/pg_dumpall.sgml,v 1.54 2005/10/15 20:12:33 neilc Exp $

PostgreSQL documentation

-->

<para>

<xref linkend="app-pgdump">. Check there for details on possible

error conditions. Also seesuppored environment variables

error conditions. Also seesupported environment variables

(<xref linkend="libpq-envars">).

</para>

</refsect1>

<!--

$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.390 2005/10/11 21:17:11 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/release.sgml,v 1.391 2005/10/15 20:12:32 neilc Exp $

Typical markup:

<listitem><para>Fix information schema view <literal>constraint_column_usage</literal> for foreign keys (Peter)</para></listitem>

<listitem><para>ECPG fixes (Michael)</para></listitem>

<listitem><para>Fix bug with multiple <literal>IN</literal> subqueries and joins in the subqueries (Tom)</para></listitem>

<listitem><para>Alllow <literal>COUNT('x')</literal> to work (Tom)</para></listitem>

<listitem><para>Allow <literal>COUNT('x')</literal> to work (Tom)</para></listitem>

<listitem><para>Install ECPG include files for Informix compatibility into separate directory (Peter)</para>

<para>

Some names of ECPG include files for Informix compatibility conflicted with operating system include files.

<listitem>

<para>

Have pg_dumpall use <command>GRANT</>/<command>REVOKE</> to dump database-levelprivleges (Tom)

Have pg_dumpall use <command>GRANT</>/<command>REVOKE</> to dump database-levelprivileges (Tom)

</para>

</listitem>

<para>

<programlisting>

Remove unused WALsegements of large transactions (Tom)

Remove unused WALsegments of large transactions (Tom)

Multiaction rule fix (Tom)

PL/pgSQL memory allocation fix (Jan)

VACUUM buffer fix (Tom)

Allow PL/pgSQL to accept non ascii identifiers (Tatsuo)

Make vacuum always flush buffers (Tom)

Fix to allow cancel while waiting for a lock (Hiroshi)

Fix for memoryaloocation problem in user authentication code (Tom)

Fix for memoryallocation problem in user authentication code (Tom)

Remove bogus use of int4out() (Tom)

Fixes for multiple subqueries in COALESCE or BETWEEN (Tom)

Fix for failure of triggers on heap open in certain cases (Jeroen van

Patch to allow vacuum on multisegment tables(Hiroshi)

R-Tree optimizer selectivity fix(Tom)

ACL file descriptor leak fix(Atsushi Ogawa)

Newexpresssion subtree code(Tom)

Newexpression subtree code(Tom)

Avoid disk writes for read-only transactions(Vadim)

Fix for removal of temp tables if last transaction was aborted(Bruce)

Fix to prevent too large row from being created(Bruce)

plpgsql fixes

Allow port numbers 32k - 64k(Bruce)

Add ^precidence(Bruce)

Add ^precedence(Bruce)

Rename sort files called pg_temp to pg_sorttemp(Bruce)

Fix for microseconds in time values(Tom)

Tutorial source cleanup

Better optimization statistics for system table access(Tom)

Better handling of non-default block sizes(Massimo)

Improve GEQO optimizer memory consumption(Tom)

UNION nowsuppports ORDER BY of columns not in target list(Jan)

UNION nowsupports ORDER BY of columns not in target list(Jan)

Major libpq++ improvements(Vince Vielhaber)

pg_dump now uses -z(ACL's) as default(Bruce)

backend cache, memory speedups(Tom)

psql and libpq now compile under Windows using win32.mak(Magnus)

Lo_read no longer stores trailing NULL(Bruce)

Identifiers are now truncated to 31 characters internally(Bruce)

Createuser options nowavailble on the command line

Createuser options nowavailable on the command line

Code for 64-bit integer supported added, configure tested, int8 type(Thomas)

Prevent file descriptor leaf from failed COPY(Bruce)

New pg_upgrade command(Bruce)

libpq's internal structures now not exported(Tom)

Allow up to 8 key indexes(Bruce)

Remove ARCHIVE key word, that is no longer used(Thomas)

pg_dump -n flag tosupress quotes around indentifiers

pg_dump -n flag tosuppress quotes around indentifiers

disable system columns for views(Jan)

new INET and CIDR types for network addresses(TomH, Paul)

no more double quotes in psql output

SCO 7/UnixWare 2.x fixes(Billy,others)

Sparc/Solaris 2.5 fixes(Ryan)

Pgbuiltin.3 is obsolete, move to doc files(Thomas)

Even moredocumention(Thomas)

Even moredocumentation(Thomas)

Nextstep support(Jacek)

Aix support(David)

pginterface manual page(Bruce)

and throw elog(ERROR) if unrecognized(Thomas)

Major large objects fix

Fix for GROUP BY showing duplicates(Vadim)

Fix for index scans inMergeJion(Vadim)

Fix for index scans inMergeJoin(Vadim)

Enhancements

------------

<programlisting>

Bug Fixes

---------

ALTER TABLE bug - runningpostgress process needs to re-read table definition

ALTER TABLE bug - runningpostgres process needs to re-read table definition

Allow vacuum to be run on one table or entire database(Bruce)

Array fixes

Fix array over-runs of memory writes(Kurt)

Fix elusive btree range/non-range bug(Dan)

Fix for hash indexes on some types like time and date

Fix for pg_log size explosion

Fix permissions on lo_export()(Bruce)

Fixunitialized reads of memory(Kurt)

Fixuninitialized reads of memory(Kurt)

Fixed ALTER TABLE ... char(3) bug(Bruce)

Fixed a few small memory leaks

Fixed EXPLAIN handling of options and changed full_path option name

European date format now set when postmaster is started

Execute lowercase function names if not found with exact case

Fixes for aggregate/GROUP processing, allow 'select sum(func(x),sum(x+y) from z'

Gist now included in thedistrubution(Marc)

Gist now included in thedistribution(Marc)

Idend authentication of local users(Bryan)

Implement BETWEEN qualifier(Bruce)

Implement IN qualifier(Bruce)

Source tree changes

-------------------

All functions now have prototypes that are compared against the calls

Allow asserts to be disabledeasly from Makefile.global(Bruce)

Allow asserts to be disabledeasily from Makefile.global(Bruce)

Change oid constants used in code to #define names

Decoupled sparc and solaris defines(Kurt)

Gcc -Wall compiles cleanly with warnings only from unfixable constructs

New config.h file(Marc, Bryan)

PG_VERSION now set to 6.0 and used by postmaster

Portability additions, including Ultrix, DG/UX, AIX, and Solaris

Reduced the number of #define's,centeralized #define's

Reduced the number of #define's,centralized #define's

Remove duplicate OIDS in system tables(Dan)

Remove duplicate system catalog info or report mismatches(Dan)

Removed many os-specific #define's

Restructured object file generation/location(Bryan, Marc)

Restructured port-specific file locations(Bryan, Marc)

Unused/uninialized variables corrected

Unused/uninitialized variables corrected

</programlisting>

</para>

</sect2>

</programlisting>

</para>

<!--

Contributors (appologies to any missed)

Contributors (apologies to any missed)

* Kurt J. Lidl &lt;lidl@va.pubnix.com&gt;

(missed in first run, but no less important)

* Erich Stamberger &lt;eberger@gewi.kfunigraz.ac.at&gt;

<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.42 2005/05/20 01:37:08 neilc Exp $ -->

<!-- $PostgreSQL: pgsql/doc/src/sgml/rules.sgml,v 1.43 2005/10/15 20:12:33 neilc Exp $ -->

<chapter id="rules">

<title>The Rule System</title>

The last command we look at is

<programlisting>

DELETE FROM computer WHEREmanufacurer = 'bim';

DELETE FROM computer WHEREmanufacturer = 'bim';

</programlisting>

Again this could result in many rows to be deleted from

<literal>computer</>. So the trigger will again run many commands

through the executor. The command generated by the rule will be

<programlisting>

DELETE FROM software WHERE computer.manufacurer = 'bim'

DELETE FROM software WHERE computer.manufacturer = 'bim'

AND software.hostname = computer.hostname;

</programlisting>

<!--

$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.353 2005/09/12 22:11:38 neilc Exp $

$PostgreSQL: pgsql/doc/src/sgml/runtime.sgml,v 1.354 2005/10/15 20:12:33 neilc Exp $

-->

<chapter Id="runtime">

</para>

<para>

The remainingsempahore settings are read-only as far as

The remainingsemaphore settings are read-only as far as

<command>sysctl</command> is concerned, but can be changed

before boot using the <command>loader</command> prompt:

<screen>

<!--

$PostgreSQL: pgsql/doc/src/sgml/user-manag.sgml,v 1.31 2005/10/13 23:26:00 tgl Exp $

$PostgreSQL: pgsql/doc/src/sgml/user-manag.sgml,v 1.32 2005/10/15 20:12:33 neilc Exp $

-->

<chapter id="user-manag">

<para>

Functions run inside the backend

server process with the operating system permissions of the

database server daemon. If theprogrammming language

database server daemon. If theprogramming language

used for the function allows unchecked memory accesses, it is

possible to change the server's internal data structures.

Hence, among many other things, such functions can circumvent any

<!--

$PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.106 2005/10/1501:47:12 neilc Exp $

$PostgreSQL: pgsql/doc/src/sgml/xfunc.sgml,v 1.107 2005/10/1520:12:33 neilc Exp $

-->

<sect1 id="xfunc">

<indexterm zone="xfunc-c-basetype">

<primary>data type</primary>

<secondary>internalorganisation</secondary>

<secondary>internalorganization</secondary>

</indexterm>

<para>