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.

full_page_writes, etc.

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

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

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

a parameter in binary format.  Also, add a TIP explaining how to use casts
in the query text to avoid needing to specify parameter types by OID.
Also fix bogus spacing --- apparently somebody expanded the tabs in the
example programs to 8 spaces instead of 4 when transposing them into SGML.

held by means of role membership, rather than directly.  Per discussion
and bug fix of a couple weeks ago.

replace use of predefined perl vars $a and $b with $x and $y - per Greg Sabino Mullane

possibility of a failure due to stack overflow when max_stack_depth is
not set properly for the platform.

fix problems with replacement-string backslashes that aren't followed by
one of the expected characters, avoid giving the impression that
replace_text_regexp() is meant to be called directly as a SQL function,
etc.

exported routines of ip.c, md5.c, and fe-auth.c to begin with 'pg_'.
Also get rid of the vestigial fe_setauthsvc/fe_getauthsvc routines
altogether.

of 4096.  Also add comment explaining why we don't suggest using
/etc/sysctl.conf to avoid needing to edit /etc/rc.

or at any rate doesn't belong as a comment in a random SGML file.

rather than British. Patch from Michael Fuhr.

documentation. Mostly add some <xref>s, fix a few typos, and
document that zlib is required in the installation docs.

the facility has been set, the facility gets set to LOCAL0 and cannot
be changed later.  This seems reasonably plausible to happen, particularly
at higher debug log levels, though I am not certain it explains Han Holl's
recent report.  Easiest fix is to teach the code how to change the value
on-the-fly, which is nicer anyway.  I made the settings PGC_SIGHUP to
conform with log_destination.