Move CREATE FUNCTION/WITH clause to end of statement to get around
 shift/reduce conflicts with type names containing "WITH".
Add lots of tokens as allowed ColId's and/or ColLabel's,
 so this should be a complete set for the v7.0 release.

We still have an internal limit in the ODBC code of 8 columns per key,
 but this should lay the groundwork for resolving that.
Includes reformulated query from Tom Lane.

if it fails to start up it (this is only vaild if -w is given).

Reorganize description of index features for more clarity.

and only one transition state, but the CREATE AGGREGATE code rejected
this combination.

Fixed bug in createdb/alternative location

reasonable, ie configure and build first, then optionally run regress
tests using new parallel (non-installed) test method, and only then
backup and kill old installation.

procedure to cover running either test script; other minor improvements.

multiple directories for --with-includes or --with-libraries.

in the foreground --- in fact, it auto-detaches.

powerpc-unknown-linux-gnu --> powerpc-unknown-linux-gnulibc1
this is because for new config.guess.

powerpc-linux-gnulibc1.

This is due to the changes made to int4.sql.

< SELECT dsqrt(float8 '64') AS eight;
<  eight
< -------
<      8
< (1 row)
<
< SELECT |/float8 '64' AS eight;
<  eight
< -------
<      8
< (1 row)
<
< SELECT ||/float8 '27' AS three;
<  three
< -------
<      3
< (1 row)
<

formatted descriptions of --with options.

file descriptor number for select().  (Suggestion from Ken Wright.)

200 MMX. I was going through my e-mail, cleaning out my 1000+ message
inbox, and found this one.  Sorry.

--
Lamar Owen

apparently copied from the makefile for the perl5 interface module,
which needs it for reasons explained in src/interfaces/Makefile.
But none of those reasons apply to plperl.

Seems to have slipped through the cracks.

neologism, apparently).

keys lists of Constraint nodes.  This eliminates a type pun that would
probably have caused trouble someday, and eliminates circular references
in the parsetree that were causing trouble now.
Also, change parser's uses of strcasecmp() to strcmp().  Since scan.l
has downcased any unquoted identifier, it is never correct to check an
identifier with strcasecmp() in the parser.  For example,
	CREATE TABLE FOO (f1 int, UNIQUE("F1"));
was accepted, which is wrong, and xlateSqlFunc did more than it should:
select datetime();
ERROR:  Function 'timestamp()' does not exist
(good)
select "DateTime"();
ERROR:  Function 'timestamp()' does not exist
(bad)

is no presorted path to compare with.

to trouble when trying to EXPLAIN VERBOSE a plan containing one.

Clean up grotty coding in them, too.  AFAICS from the CVS logs, these
have been broken since Postgres95, so I'm not going to insist on an
initdb to fix them now...

it in a separate object.  There's no value in keeping the state separate,
and it creates dangling-pointer problems.  Also, remove PQsetenv routines
from public API, until and unless they are redesigned to have a safer
interface.  Since they were never part of the documented API before 7.0,
it's unlikely that anyone is calling them.

to avoid undue sensitivity to roundoff error, believe that a zero
or slightly negative range estimate should represent a small
positive selectivity, rather than falling back on a generic default
estimate.