specified index access method.  Clean up wording of some existing error
messages, too.

fsync settings, so the -F option no longer needs to be treated as secure.

libpq++.h contained copies of the class declarations in the other libpq++
include files, which was bogus enough, but the declarations were not
completely in step with the real declarations.  Remove these in favor
of including the headers with #include.  Make PgConnection destructor
virtual (not absolutely necessary, but seems like a real good idea
considering the number of subclasses derived from it).  Give all classes
declared private copy constructors and assignment operators, to prevent
compiler from thinking it can copy these objects safely.

not a bare database name.

compiler than the one selected to build Postgres with.  It was trying
to feed Postgres-compiler switches to Tcl's compiler.  (Seen this before
with the perl5 interface...) Fix to use only CFLAGS taken from Tcl's
configure information, plus -I which is pretty universal.

unless you feed it -Aa or -Ae switch.  Autoconf does not know about this,
but we can fix it in the hpux_cc template file.  I knew templates were
good for something ;-)

gcc doesn't think these are a problem, but somewhere out there is a
compiler that will spit up.

'Twas my fault, I think.

know if that case ever breaks again...

to give wrong results: it should be looking at inJoinSet not inFromCl.
Also, make 'modified' flag be local to ApplyRetrieveRule: we should
append a rule's quals to the query iff that particular rule applies,
not if we have fired any previously-considered rule for the query!

Move several platforms to the unsupported list :(

as 'alphaev5', cf report from Stepanov 13-Apr-00.

(SELECT FROM table*).  Cause was reference to 'eref' field of an RTE,
which is null in an RTE loaded from a stored rule parsetree.  There
wasn't any good reason to be touching the refname anyway...

table for an average of NTUP_PER_BUCKET tuples/bucket, but cost_hashjoin
was assuming a target load of one tuple/bucket.  This was causing a
noticeable underestimate of hashjoin costs.

and errors from pickier compilers.

Not a big step forward, but it's something...

estimation operators.  See contrib/likeplanning/README for info.