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

interval_justify_hours in timestamp subtraction.  TODO already has text
description.

< 	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

for an outer join; symptom is bogus error "RIGHT JOIN is only supported with
merge-joinable join conditions".  Problem was that select_mergejoin_clauses
did its tests in the wrong order.  We need to force left join not right join
for a merge join when there are non-mergeable join clauses; but the test for
this only accounted for mergejoinability of the clause operator, and not
whether the left and right Vars were of the proper relations.  Per report
from Jean-Pierre Pelletier.

>
> 	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.

some small stylistic improvements in these functions.  Also fix several
places where TMODULO() was being used with wrong-sized quotient argument,
creating a risk of overflow --- interval2tm was actually capable of going
into an infinite loop because of this.

to the main thread.  This allows removal of WaitForSingleObjectEx() calls
from the main thread, thereby allowing us to re-enable Qingqing Zhou's
CHECK_FOR_INTERRUPTS performance improvement.  Qingqing, Magnus, et al.

Sergey E. Koposov

maintenance level 5300-03; the following patch adds documentation to
FAQ_AIX.

Chris Browne

> * 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().

one CHECK_FOR_INTERRUPTS() call, so that you can control-C out of the
loop.  Reported by Merlin Moncure.

of RHEL 4.  Update supported-platforms list accordingly.

update configure and bugtemplate for beta 4 ...

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

full_page_writes, etc.

type time with time zone, ie, +/- 13:59 not +/- 12:00.  Also some minor
wording improvements.

WaitForSingleObjectEx is always called by CHECK_FOR_INTERRUPTS.  This
should be reinstated but the setitimer() emulation will have to be
redesigned first.

minor code cleanup - replace useless struct timezone argument to
gettimeofday with NULL in a few places, making it consistent with
usage elsewhere.

a kernel call unless there's some evidence of a pending signal.  This should
bring its performance on Windows into line with the Unix version.  Problem
diagnosis and patch by Qingqing Zhou.  Minor stylistic tweaks by moi ...
if it's broken, it's my fault.

the code actually does, and needed copy-editing anyway.  Also take the
opportunity to expand the section on routine reindexing.

properly advancing the CommandCounter between multiple sub-queries
generated by rules, we forgot to update the snapshot being used, so
that the successive sub-queries didn't actually see each others'
results.  This is still not *exactly* like the semantics of normal
execution of the same queries, in that we don't take new transaction
snapshots and hence don't see changes from concurrently committed
commands, but I think that's OK and probably even preferable for
EXPLAIN ANALYZE.

of the form nextval('foo'::varchar) doesn't break.  Per gripe from
Jean-Pierre Pelletier.  Initdb forced :-(

an example function.

documenting GiST crash recovery procedures, as requested some time ago
by Teodor.  (The GiST chapter doesn't seem quite the right place for
the latter, but I'm not sure what else to do with it.)