< * -Allow triggers to be disabled [trigger]
> * -Allow triggers to be disabled

has to be tested dynamically if we want to make portable executables.
Chuck McDevitt and Andrew Dunstan.

fix up a few references to 8.1devel -> 8.1beta1

going to keep it after all.

< 	  Logically, a reload should set the same values as a
<           server restart.

This might be overly conservative, but we know it does not work on amd64.
Per buildfarm results.

<           Currently, if a variable is commented out, it keeps the
<           previous uncommented value until a server restarted.
> 	  Currently, if a variable is commented out, it keeps the
> 	  previous uncommented value until a server restarted.
> 	  Logically, a reload should set the same values as a
>           server restart.

'my' where appropriate.  Michael Fuhr

in plperl functions.

cleanup.

fly.  Fix problem with incompletely duplicated setup code.  Andrew Dunstan,
from an idea of Michael Fuhr's.

> * Add sleep() function, remove from regress.c

is not adequately tested yet, but let's get it into beta1 so it can be
tested.  Magnus Hagander and Tom Lane.

triggers exist but are all disabled.  Problem noted by Gavin Sherry in
original discussion of enable/disable trigger patch, but was never
addressed.

> 	o Add sleep() to PL/PgSQL

Jim C. Nasby

< 	o Do VACUUM FULL if table is nearly empty?
> 	o Suggest VACUUM FULL if a table is nearly empty

>
>           Currently, if a variable is commented out, it keeps the
>           previous uncommented value until a server restarted.
>

        - Remove stary character from string quoting.
        - Fixed check to report missing varchar pointer implementation.

< * Allow triggers to be disabled [trigger]
> * -Allow triggers to be disabled [trigger]
> * Allow triggers to be disabled in only the current session.
<   Currently the only way to disable triggers is to modify the system
<   tables.
>   This is currently possible by starting a multi-statement transaction,
>   modifying the system tables, performing the desired SQL, restoring the
>   system tables, and committing the transaction.  ALTER TABLE ...
>   TRIGGER requires a table lock so it is not idea for this usage.