<para>

Time zones, and time-zone conventions, are influenced by

political decisions, not just earth geometry. Time zones around the

world became somewhat standardized during the1900's,

world became somewhat standardized during the1900s,

but continue to be prone to arbitrary changes, particularly with

respect to daylight-savings rules.

<productname>PostgreSQL</productname> uses the widely-used

correctly. Advisory locks can be useful for locking strategies

that are an awkward fit for the MVCC model.

For example, a common use of advisory locks is to emulate pessimistic

locking strategies typical of socalled <quote>flat file</> data

locking strategies typical of so-called <quote>flat file</> data

management systems.

While a flag stored in a table could be used for the same purpose,

advisory locks are faster, avoid table bloat, and are automatically

(useful when multiple scripts were specified with <literal>-f</>),

and <replaceable>time_epoch</>/<replaceable>time_us</> are a

UNIX epoch format timestamp and an offset

in microseconds (suitable for creatinga ISO 8601

in microseconds (suitable for creatingan ISO 8601

timestamp with fractional seconds) showing when

the transaction completed.

</para>

</synopsis>

<para>

Encrypt <parameter>data</> with a public PGP key <parameter>key</>.

Giving this function a secret key will producea error.

Giving this function a secret key will producean error.

</para>

<para>

The <parameter>options</> parameter can contain option settings,

Sometimes it is desirable to write Tcl functions that are not restricted

to safe Tcl. For example, one might want a Tcl function that sends

email. To handle these cases, there is a variant of <application>PL/Tcl</> called <literal>PL/TclU</>

(for untrusted Tcl). This isthe exact same language except that a full

(for untrusted Tcl). This isexactly the same language except that a full

Tcl interpreter is used. <emphasis>If <application>PL/TclU</> is used, it must be

installed as an untrusted procedural language</emphasis> so that only

database superusers can create functions in it. The writer of a <application>PL/TclU</>

statements in <literal>WITH</>, the order in which the specified updates

actually happen is unpredictable. All the statements are executed with

the same <firstterm>snapshot</> (see <xref linkend="mvcc">), so they

cannot <quote>see</>each others' effects on the target tables. This

cannot <quote>see</>one another's effects on the target tables. This

alleviates the effects of the unpredictability of the actual order of row

updates, and means that <literal>RETURNING</> data is the only way to

communicate changes between different <literal>WITH</> sub-statements and

</programlisting>

<para>

The following example command changes the language option to dutch,

The following example command changes the language option to<literal>dutch</>,

and removes the stopword option entirely.

</para>

COMMENT ON TABLE my_schema.my_table IS 'Employee Information';

COMMENT ON TABLESPACE my_tablespace IS 'Tablespace for indexes';

COMMENT ON TEXT SEARCH CONFIGURATION my_config IS 'Special word filtering';

COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer forswedish language';

COMMENT ON TEXT SEARCH DICTIONARY swedish IS 'Snowball stemmer forSwedish language';

COMMENT ON TEXT SEARCH PARSER my_parser IS 'Splits text into words';

COMMENT ON TEXT SEARCH TEMPLATE snowball IS 'Snowball stemmer';

COMMENT ON TRIGGER my_trigger ON my_table IS 'Used for RI';

</para>

<para>

This enabled <command>GRANT</command> to give other users the

ability to grant privileges ona object.

ability to grant privileges onan object.

</para>

</listitem>

</itemizedlist>

<para>

The new syntax is <link linkend="SQL-CREATEINDEX"><command>CREATE

INDEX CONCURRENTLY</></link>. The default behavior is

still to block table modification whilea index is being

still to block table modification whilean index is being

created.

</para>

</listitem>

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 to suppress quotes aroundindentifiers

pg_dump -n flag to suppress quotes aroundidentifiers

disable system columns for views(Jan)

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

no more double quotes in psql output

(e.g. "DATETIME 'now'")(Thomas)

Add conversions for int2, int4, and OID types to and from text(Thomas)

Use shared lock when building indexes(Vadim)

Free memory allocated foran user query inside transaction block after

Free memory allocated fora user query inside transaction block after

this query is done, was turned off in &lt;= 6.2.1(Vadim)

New SQL statement CREATE PROCEDURAL LANGUAGE(Jan)

New <productname>PostgreSQL</productname> Procedural Language (PL) backend interface(Jan)

New tools:

* pgperl - a Perl (4.036) interface to Postgres95

* pg_dump - a utility for dumping out a postgres database into a

script file containing query commands. The script files are ina ASCII

script file containing query commands. The script files are inan ASCII

format and can be used to reconstruct the database, even on other

machines and other architectures. (Also good for converting

a Postgres 4.2 database to Postgres95 database.)

;; By default, the part and reference title pages get wrong page

;; numbers: The first title page gets roman numerals carried over from

;; preface/toc -- we wantarabic numerals. We also need to make sure

;; preface/toc -- we wantArabic numerals. We also need to make sure

;; that page-number-restart is set of #f explicitly, because otherwise

;; it will carry over from the previous component, which is not good.

;;

</programlisting>

where the colon (<symbol>:</symbol>) symbol acts as a delimiter between a

aphrase and its replacement.

phrase and its replacement.

</para>

<para>

<para>

The calling <command>SELECT</> statement doesn't necessarily have be

bejust <literal>SELECT *</> &mdash; it can reference the output

just <literal>SELECT *</> &mdash; it can reference the output

columns by name or join them to other tables. The function produces a

virtual table with which you can perform any operation you wish (e.g.

aggregation, joining, sorting etc). So we could also have:

<para>

Unlike commutators, a pair of unary operators could validly be marked

as eachothers' negators; that would mean (A x) equals NOT (B x)

as eachother's negators; that would mean (A x) equals NOT (B x)

for all x, or the equivalent for right unary operators.

</para>