Euler Taveira de Oliveira

Euler Taveira de Oliveira

> * MONEY dumps in a locale-specific format making it difficult to
>   restore to a system with a different locale

Brendan Jurd

Some additional minor editorializing by Tom.

> 	o Have ALTER SEQUENCE RENAME rename the sequence name stored
> 	  in the sequence table
>
> 	  http://archives.postgresql.org/pgsql-bugs/2007-09/msg00092.php
> 	  http://archives.postgresql.org/pgsql-bugs/2007-10/msg00007.php
>

on CORE previously.

This module offers transaction ID's containing the original XID and the
transaction epoch as a bigint value to the user level. It also provides
a special txid_snapshot data type that contains an entire transactions
visibility snapshot information, which is useful to determine if a
particular txid was visible to a transaction or not.

The module has been tested by porting Slony-I from using its original
xxid data type.

Jan

also" entries for autovacuum in analyze and vacuum reference pages, and
enhance usage of cross-references in the maintenance page.

to do "make DRAFT=Y html"; you need to use "make draft" (which was also
supported previously).

as we do (and upstream Tcl doesn't).  The loop limit might be subject
to negotiation if anyone ever tries to do regex debugging in Far
Eastern languages, but for now 1000 seems plenty.  CHR_MAX was right out :-(

warnings on a 64-bit machine.  Noted while chasing a recent regex
bug report.

are converted to Postgres Assert() macros, instead of using <assert.h>
as formerly.  No difference in production builds, but --enable-cassert
debug builds will get better coverage for regex testing.

passing on errors from the language interpreter.  (plpython seems
fairly OK about this already.)  Per gripe from Robert Kleemann.

have back branch activity.  This will be useful for creating release
notes for major releases.

generation ... we should figure this out later ...

tag it 8.3beta1 ... the beta cycle begins

made and removed at the correct times.

which evidently it got as an unofficial export from pgtypeslib.

eval_const_expressions simplifies this to just "WHERE false", but we have
already done pull_up_IN_clauses so the IN join will be done, or at least
planned, anyway.  The trouble case comes when the sub-SELECT is itself a join
and we decide to implement the IN by unique-ifying the sub-SELECT outputs:
with no remaining reference to the output Vars in WHERE, we won't have
propagated the Vars up to the upper join point, leading to "variable not found
in subplan target lists" error.  Fix by adding an extra scan of in_info_list
and forcing all Vars mentioned therein to be propagated up to the IN join
point.  Per bug report from Miroslav Sulc.

Might as well have the latest when we wrap 8.3beta1.

per the example of libpq/Makefile.

around the icc bug exhibited by buildfarm member dugong.

a minor markup improvement.

left to made, but this is a start.

where possible, add overview and incompatibilities lists, minor cleanups.
The SGML-ification still leaves much to be desired.

names.  ITAGAKI Takahiro