< * Prevent long-lived temporary tables from causing frozen-Xid advancement
> * Prevent long-lived temporary tables from causing frozen-xid advancement
>
>    The problem is that autovacuum cannot vacuum them to set frozen xids;
>    only the session that created them can do that.
>
>
>

relying on stringinfo.c.  This fixes a problem reported by Marko Kreen, but I
didn't use his patch, per subsequent discussion.

ItemPointerData.

opfuncid of an OpExpr initially, considering that it has the information
at hand already.  We'll still treat opfuncid as a cache rather than a
guaranteed-valid value, but this change saves one more syscache lookup
in the normal code path.

OpExpr and related nodes.  We're going to have to set the opfuncid of
such nodes eventually (if we haven't already), so we might as well
exploit the opportunity to cache the function OID.  Buys back some
of the extra planner overhead noted by Guillaume Smet, though I still
need to fool with equivclass.c to really respond to that.

"bool" into plperl.c.  This has always been a hazard since Perl allows a
platform-specific choice to define bool as int rather than char, but
evidently this didn't happen on any platform we support ... until OS X 10.5.
Per report from Brandon Maust.

Back-patch as far as 8.0 --- a bit arbitrary, but it seems unlikely anyone
will be trying to port 7.x onto new platforms.

used.

(conflicting values).

so new thousands separator doesn't match decimal symbol.

happened to be right up against the end of memory, per report from
Matt Magoffin.  While at it, avoid useless multiple copying of string
by not depending on xmlStrncatNew.

release notes.

Adjust contrib/tsearch2 regression results to use XML tag and XML entity descriptions, as now used by core text search default parser.

Re-order some items as migration changes.

Allow tag and entity names that follow XML rules. Provide for hexadecimal
as well as decimal numeric entities. Adjust code names to coincide with
new descriptions.

< 	o Prevent COMMENT ON dbname from issuing a warning when loading
< 	  into a database with a different name, perhaps using COMMENT ON
< 	  CURRENT DATABASE
> 	o Change pg_dump so that a comment on the dumped database is
> 	  applied to the loaded database, even if the database has a
> 	  different name.  This will require new backend syntax, perhaps
> 	  COMMENT ON CURRENT DATABASE.

< 	o Allow COMMENT ON dbname to work when loading into a database
< 	  with a different name, perhaps using COMMENT ON CURRENT
<           DATABASE
> 	o Prevent COMMENT ON dbname from issuing a warning when loading
> 	  into a database with a different name, perhaps using COMMENT ON
> 	  CURRENT DATABASE

< 	  with a different name
> 	  with a different name, perhaps using COMMENT ON CURRENT
>           DATABASE
>

databases.

> 	o Allow COMMENT ON dbname to work when loading into a database
> 	  with a different name

A bunch of other desultory copy-editing, too.

ambiguity and say what the default value is.

plans.

item to #1 imcompatibility slot.

GetMemoryChunkSpace, not just the palloc request size.  This brings the
allocatedMemory counter close enough to reality (as measured by
MemoryContextStats printouts) that I think we can get rid of the arbitrary
factor-of-2 adjustment that was put into the code initially.  Given the
sensitivity of GIN build to work memory size, not using as much of work
memory as we're allowed to seems a pretty bad idea.