that OS=hpux is the same as CPU=hppa.  First steps at doing this.
With these patches, we still work on hppa with either gcc or HP's cc.
We might work on hpux/itanium with gcc, but I can't test it.  Definitely
will not work on hpux/itanium with non-gcc compiler, for lack of spinlock
code.

from --with-includes.

and consistency.

uselessly invoke it in parallel in the first place.

rather than parsing the message.  Add some documentation about embedded
SQL.

- Added just another pgtypeslib function.

python needs to be removed from here

clean python out of Makefile

remove python module, as its moved to http://www.pygresql.org

Havard Eidnes.

might have inherited from the environment that would possibly cause
psql to fail to connect to the temp installation properly.  Per trouble
report from Markus Bertheau 7/1/03.

function is not found.  Also, make all the PL libraries have initialization
functions with standard names.  Patch from Joe Conway.

the actual logical structure and quoting rules being used.  Fixes bug
reported by Chris K-L on 7/8/03.

> * Implement dirty reads or shared row locks and use them in RI triggers

> * Implement dirty reads or shared locks and use them in RI triggers

Rod Taylor

  There is an option "-s oldname=newname", which changes the old field name of
  the dbf-file to the newname in PostgeSQL. If the length of the new name is 0,
  the field is skiped. If you want to skip the first field of the dbf-file,
  you get the wildest error-messages from the backend.
  dbf2pg load the dbf-file via "COPY tablename FROM STDIN". If you skip the
  first field, it is an \t to much in STDIN.

A fix could be an counter j=0, which increments only, if a field is imported
(IF (strlen(fields[h].db_name)> 0) j++. And only if j > 1 (if an other field is
imported) the \t is printed.

An other small bug in the README:
-s start
              Specify  the  first record-number in the xBase-file
              we will insert.
should be
-e start
              Specify  the  first record-number in the xBase-file
              we will insert.

Thomas Behr

Patch from Andreas Pflug.

> * Allow server log information to be output as INSERT statements

float8smaller, float8larger (and thereby the MIN/MAX aggregates on these
datatypes) to agree with the datatypes' comparison operations as
regards NaN handling.  In all these datatypes, NaN is arbitrarily
considered larger than any normal value ... but MIN/MAX had not gotten
the word.  Per recent discussion on pgsql-sql.