Andrew Dunstan

that has parameters is always planned afresh for each Bind command,
treating the parameter values as constants in the planner.  This removes
the performance penalty formerly often paid for using out-of-line
parameters --- with this definition, the planner can do constant folding,
LIKE optimization, etc.  After a suggestion by Andrew@supernews.

Per buildfarm results.

pointers are int64, but warnings are emitted for position info in
error messages in parser, so, just cast it to int32

Michael Glaesemann

Marko Kreen

can create or modify rules for the table.  Do setRuleCheckAsUser() while
loading rules into the relcache, rather than when defining a rule.  This
ensures that permission checks for tables referenced in a rule are done with
respect to the current owner of the rule's table, whereas formerly ALTER TABLE
OWNER would fail to update the permission checking for associated rules.
Removal of separate RULE privilege is needed to prevent various scenarios
in which a grantee of RULE privilege could effectively have any privilege
of the table owner.  For backwards compatibility, GRANT/REVOKE RULE is still
accepted, but it doesn't do anything.  Per discussion here:
http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php

fix suggestion from Peter.

'GIN FailedAssertions on Itanium2 with Intel compiler' in pgsql-hackers,
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01914.php

Per discussion
http://archives.postgresql.org/pgsql-hackers/2006-08/msg01409.php

dbase, dbmirror, fulltextindex, mac, userlock; or abandoned: mSQL-interface,
tips.

Added some interval checks to regression suite.

Fixed ecpglib trying to read one character after end-of-string.
Fixed port number setting in regression suite.

Christopher Kings-Lynne

Bruce, Michael Glaesemann

Jun Kuwamura

position_in_unique_constraint (column newly added per SQL2003).
Greg Mullane

Albe Laurenz

second scan of table).

Gregory Stark

Magnus Hagander

the target relation(s).  There might be some cases where we could discard
the pending event instead, but for the moment a conservative approach
seems sufficient.  Per report from Markus Schiltknecht and subsequent
discussion.

of 'S', and the views were not checking for table visibility with
regards to temporary tables and sequences.

Greg Sabino Mullane

Christopher Kings-Lynne

Simon Riggs

some platforms.

working in a multibyte encoding.  This fixes the problems exhibited in
bug #1931 and other reports of ILIKE misbehavior in UTF8 encoding.
It's a pretty grotty solution though --- should rethink how to do it
after we install better locale support, someday.

Author: Victor Wagner <vitus@cryptocom.ru>