the trigger is attached to in the hashkey.  This ensures that we will
create separate compiled trees for each table the trigger is used with,
avoiding possible datatype-mismatch problems if the tables have different
rowtypes.  This is essentially the same bug recently identified in plpython
--- though plpgsql doesn't seem as prone to crash when the rowtype changes
underneath it.  But failing robustly is no substitute for just working.

> * -Add btree index support for reltime, tinterval, regproc (Tom)

be anything yielding an array of the proper kind, not only sub-ARRAY[]
constructs; do subscript checking at runtime not parse time.  Also,
adjust array_cat to make array || array comply with the SQL99 spec.

Joe Conway

No change in behavior, but old code would have failed to detect
overrun of MAX_LOCKMODES.

are now driven by the default btree opclass, rather than assuming that
particular operator names have the needed semantics.

datatype by array_eq and array_cmp; use this to solve problems with memory
leaks in array indexing support.  The parser's equality_oper and ordering_oper
routines also use the cache.  Change the operator search algorithms to look
for appropriate btree or hash index opclasses, instead of assuming operators
named '<' or '=' have the right semantics.  (ORDER BY ASC/DESC now also look
at opclasses, instead of assuming '<' and '>' are the right things.)  Add
several more index opclasses so that there is no regression in functionality
for base datatypes.  initdb forced due to catalog additions.

> * Allow PREPARE of cursors

This useless routine will removed in 7.5. It's already discussed (see
hackers list archive).

Karel Zak

> * Fix upper()/lower() to work for multibyte encodings
>

spelling mistake in the PREPARE ref page (2) Makes some
English more consistent, in the ref pages for some of the
client apps (3) Adds a link to the libpq docs in the
vacuumdb ref page.

Neil Conway

have cursors that might outlive their creating transactions. A
patch is attached that fixes this (suggestions on better wording
are welcome).

Neil Conway

> * Allow pooled connections to query prepared queries
> * Allow pooled connections to close all open WITH HOLD cursors

any use of CIDR masks - here's a patch that adds  a couple of  sample
lines and associated comments.

Andrew Dunstan

binary format read/created by COPY BINARY. It also mentions the
contrib/binarycopy module.

Lee Kindness.

> * Add ALTER DOMAIN, AGGREGATE, CONVERSION, SEQUENCE ... OWNER TO
>

> * Add TRUNCATE ... CASCADE

> * Add pg_get_acldef(), pg_get_typedefault(), and pg_get_attrdef()

"syslog" option.)

By the way: The "virtual_host" parameter is a bad name for that
particular option, I think. "Virtual host" signals that PostgreSQL will
behave differently according to which IP address it's contacted (like
Apache's virtual host support which makes the web-server serve different
sites according to different criteria). A better word for the options
would be "tcpip_listen_addr" or something like that.

Troels Arvin

configure to report if they are not found.

and test them, in addition to testing the underlying LargeObject API methods.

 Modified Files:
 	jdbc/build.xml jdbc/org/postgresql/test/jdbc2/BlobTest.java

using the V3 protocol.

 Modified Files:
 	jdbc1/AbstractJdbc1Connection.java

faster, but more importantly does not leak memory.  Still needs more work
though, per my recent note to pgsql-hackers.

initial response is 'S', not 'Y', when it is willing to do SSL.

the #includes it depends on.