refcursors.

timestamp.

Jun Kuwamura

volatile), rather than the old cachable/noncachable distinction.  This
allows indexscan optimizations in many places where we formerly didn't.
Also, add a pronamespace column to pg_proc (it doesn't do anything yet,
however).

A new pg_hba.conf column, USER
Allow specifiction of lists of users separated by commas
Allow group names specified by +
Allow include files containing lists of users specified by @
Allow lists of databases, and database files
Allow samegroup in database column to match group name matching dbname
Removal of secondary password files
Remove pg_passwd utility
Lots of code cleanup in user.c and hba.c
New data/global/pg_pwd format
New data/global/pg_group file

and/or with GUC variables.

depend on this rather than the trigger argument strings to locate the
other relation to test.  This makes RI triggers function properly in
the presence of schemas and temp tables.  Along the way, fix bogus lack
of locking in RI triggers, handle quoting of names fully correctly,
compute required sizes of query buffers with some semblance of accuracy.

path.  The default behavior if no per-user schemas are created is that
all users share a 'public' namespace, thus providing behavior backwards
compatible with 7.2 and earlier releases.  Probably the semantics and
default setting will need to be fine-tuned, but this is a start.

in different namespaces.  Also, cleanup work on relation namespace
support: drop, alter, rename commands work for tables in non-default
namespaces.

in schemas other than the system namespace; however, there's no search
path yet, and not all operations work yet on tables outside the system
namespace.

 Allow EXECUTE of "CREATE TABLE AS ... SELECT" in PL/PgSQL (Tom)

 Allow CREATE TABLE AS ... SELECT in PL/PgSQL (Tom)

Also, fix debug logging of parse/plan trees so that the messages actually
go through elog(), not directly to stdout.

there and CREATE SCHEMA will make entries in it...

the parsetree representation.  As yet we don't *do* anything with schema
names, just drop 'em on the floor; but you can enter schema-compatible
command syntax, and there's even a primitive CREATE SCHEMA command.
No doc updates yet, except to note that you can now extract a field
from a function-returning-row's result with (foo(...)).fieldname.

> > to perform sql command:
> >  update pg_amop set amopreqcheck = true where amopclaid =
> >       (select oid from pg_opclass where opcname = 'gist_txtidx_ops');
>
> Oleg, sorry, I don't understand where this should appear.  In the README
> file, and if so, where?  Is this something only for people upgrading
> from 7.2?

Sorry Bruce, I was unclear. I have attached patch to Readme.tsearch
Also, It'd be worth to mention in Changes to point users of tsearch
about importang upgrade notices.

Oleg Bartunov

Rod Taylor.

	Ensure that sequence counters do not go backwards after a crash

! 	DIFFERENCE (− or ∖): builds the set difference of
  	two tables. Let <classname>R</classname> and
<classname>S</classname>
again be two tables with the same
  	arity. <classname>R</classname> - <classname>S</classname>
--- 488,494 ----

        <listitem>
        <para>
! 	EXCEPT (&minus; or &setmn;): builds the set difference of

file that SIGHUP or "pg_ctl reload" are required for changes to take
affect on a running server.