necessary, and be careful to refer to the right version where it is
useful to do so.  This partially reverts an ill-considered search and
replace from a few months ago.

elsewhere.

From Simon Riggs; cleanup and editorialization by Neil Conway.

referential integrity relationships.

Andreas Seltenreich

< 	o Allow ALTER TABLE RENAME CONSTRAINT
> 	o Add ALTER TABLE RENAME CONSTRAINT, update index name also

> 	o Have ALTER INDEX update the name of a constraint using that index
> 	o Allow ALTER TABLE RENAME CONSTRAINT

commands.  Per complaint that \df+ is clearer in expanded mode.

< 	o Add a GUC variable to allow output of interval values in ISO8601
< 	  format
212a211,223
> 	o Add a GUC variable to allow output of interval values in ISO8601
> 	  format
> 	o Improve timestamptz subtraction to be DST-aware
>
> 	  Currently, subtracting one date from another that crosses a
> 	  daylight savings time adjustment can return '1 day 1 hour', but
> 	  adding that back to the first date returns a time one hour in
> 	  the future.  This is caused by the adjustment of '25 hours' to
> 	  '1 day 1 hour', and '1 day' is the same time the next day, even
> 	  if daylight savings adjustments are involved.
>
> 	o Fix interval display to support values exceeding 2^31 hours
> 	o Add overflow checking to timestamp and interval arithmetic

Jeff Frost, it may be necessary to ignore specific exit codes.

inFromCl true, meaning that they will list out as explicit RTEs if they
are in a view or rule.  Update comments about inFromCl to reflect the way
it's now actually used.  Per recent discussion.

Simon Riggs

>
> 	o Add auto-expanded mode so expanded output is used if the row
> 	  length is wider than the screen width.
>
> 	  Consider using auto-expanded mode for backslash commands like \df+.

English, and fix the incorrect example.

Sergey E. Koposov

> * Allow user-defined functions retuning a domain value to enforce domain
>   constraints

Fix incorrect wording about function failure time on unsafe ops - these
are now caught by the validator. And a small visit from the perl style police:
check the return value from open().

PQregisterThreadLock().

I also remove the crypt() mention in the libpq threading section and
added a single sentence in the client-auth manual page under crypt().
Crypt authentication is so old now that a separate paragraph about it
seemed unwise.

I also added a comment about our use of locking around pqGetpwuid().

of RHEL 4.  Update supported-platforms list accordingly.

while tar is copying it.  This behavior is unhelpful when taking a base
backup.  Per gripe from Pallav Kalva back in April.