| Age | Commit message (Collapse) | Author |
|---|
|
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.
|
|
costs using the inner path's parent->rows count as the number of tuples
processed per inner scan iteration. This is wrong when we are using an
inner indexscan with indexquals based on join clauses, because the rows
count in a Relation node reflects the selectivity of the restriction
clauses for that rel only. Upshot was that if join clause was very
selective, we'd drastically overestimate the true cost of the join.
Fix is to calculate correct output-rows estimate for an inner indexscan
when the IndexPath node is created and save it in the path node.
Change of path node doesn't require initdb, since path nodes don't
appear in saved rules.
|
|
|
|
|
|
Update those to latest Autoconf sources, too.
|
|
Reported by "Tibor Laszlo" <ltibor@mail.tiszanet.hu> and fix suggested by
"Hiroshi Inoue" <Inoue@tpf.co.jp>.
|
|
is available yet.
Remove redundant call to xlateSqlType() in the character
type handling code.
|
|
|
|
to simplify constant expressions and expand SubLink nodes into SubPlans
is done in a separate routine subquery_planner() that calls union_planner().
We formerly did most of this work in query_planner(), but that's the
wrong place because it may never see the real targetlist. Splitting
union_planner into two routines also allows us to avoid redundant work
when union_planner is invoked recursively for UNION and inheritance
cases. Upshot is that it is now possible to do something like
select float8(count(*)) / (select count(*) from int4_tbl) from int4_tbl
group by f1;
which has never worked before.
|
|
|
|
|
|
|
|
|
|
';' operators.
|
|
|
|
|
|
|
|
entries in template selection rules. Also, change alpha-dec-osf pattern
to cope with version info attached to the 'alpha' part.
|
|
|
|
command, the entries in template/.similar can really be regular
expressions. This isn't a new feature, just an observation of what the
code already did.
|
|
incorrect use of StrNCpy.
|
|
leading to postmaster accepting args 1 shorter than it had room for.
|
|
Fix inadequate parenthesization in several other macros.
|
|
|
|
|
|
|
|
had already been transformed. This led to failure in examples like
UPDATE table SET fld = (SELECT ...). Repair this, and revise the
comments to explain that transformExpr has to be robust against this
condition. Someday we might want to fix the callers so that
transformExpr is never invoked on its own output, but that someday
is not today.
|
|
user, so it doesn't need to be translated from the number to the name.
also ``create database ...'' does not take numbers for the encoding, so
the ENCODING variable does not need to be translated to a number, but left
as the text representation. a patch is supplied to make the changes i
have found to work. i was successful dumping and reloading my database
after these changes.
-
John M. Flinchbaugh
|
|
incorrect descriptions of a couple of log-related functions.
I will not force an initdb for this, but log() on a numeric won't
work until you do one...
|
|
In function parsing, try for an actual function of the given name and
input types before trying to interpret the function call as a type
coercion request, rather than after. Before, a function that had the
same name as a type and operated on a binary-compatible type wouldn't
get invoked. Also, cross-pollinate between func_select_candidates and
oper_select_candidates to ensure that they use as nearly the same
resolution rules as possible. A few other minor code cleanups too.
|
|
actually returns the type it is named for.
|
|
|
|
|
|
problem could be lack of parentheses. This addresses cases like
X UserOp UserOp Y, which will be parsed as (X UserOp) UserOp Y,
whereas what likely was wanted was X UserOp (UserOp Y).
|
|
|
|
16-Mar-00: trailing + or - is not part of the operator unless the operator
also contains characters not present in SQL92-defined operators. This
solves the 'X=-Y' problem without unduly constraining users' choice of
operator names --- in particular, no existing Postgres operator names
become invalid.
Also, remove processing of // comments, as agreed in the same thread.
|
|
|
|
prefix operator :-(. Bad enough that we have no implementation of
unary plus, but at least with this fix the grammar will take it.
|
|
|
