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.

easy (maybe dumb) fix for 5 in attachment define.patch

greetings, Andreas

patch in a second. Should be sufficent to just make sure the first
character is a '/', right?

Ross J. Reedstrom

1. C++ style comments in C source for ecpg ( // comment )
2. compiler finds wrong include file extern.h in ecpg/lib/descriptor.c
from
include path instead of workdir (rename it ?)
3. fe-connect getsockopt takes a socklen_t as fifth arg not int (use
SOCKET_SIZE_TYPE instead)
4. char vs unsigned char in psql calls to libpq
5. empty define that results in an empty but terminated line ( ; )

Now for all but point 3 I can supply changes to the
compiler flags, to make the compiler less pedantic.
Or is someone interested in the complications ?

in the meantime can someone apply the attached patch ?

Andreas

allow to write applications which do not have a link to postgres_ext.h in
their source directory.

Andreas Kardos

cases but actually did no such thing.  Make it test some more cases than
before (including things that didn't work in 6.5).

input, not throw a gratuitous elog().

outside WHERE clause.  Fix a couple of places that didn't handle uplevel
refs cleanly.

nodes introduced by make_subplan().  It'd be better if we used a
different node type for subplan result placeholders, but for now...

Const placeholder nodes for subplan result values.

use a default value that's fairly small.  We were generating a result
of about 0.1, but I think 0.01 is probably better --- want to encourage
use of an indexscan in this situation.

to more than one character, and try to do the right thing in non-ASCII
locales.