- 26 3月, 2000 6 次提交
-
-
由 Tom Lane 提交于
file descriptor number for select(). (Suggestion from Ken Wright.)
-
由 Bruce Momjian 提交于
200 MMX. I was going through my e-mail, cleaning out my 1000+ message inbox, and found this one. Sorry. -- Lamar Owen
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
Seems to have slipped through the cracks.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
neologism, apparently).
-
- 25 3月, 2000 7 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
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)
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
is no presorted path to compare with.
-
- 24 3月, 2000 12 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
to trouble when trying to EXPLAIN VERBOSE a plan containing one.
-
由 Tom Lane 提交于
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...
-
由 Tom Lane 提交于
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.
-
由 Tatsuo Ishii 提交于
-
由 Bruce Momjian 提交于
-
由 Tom Lane 提交于
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.
-
由 Bruce Momjian 提交于
easy (maybe dumb) fix for 5 in attachment define.patch greetings, Andreas
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
patch in a second. Should be sufficent to just make sure the first character is a '/', right? Ross J. Reedstrom
-
由 Bruce Momjian 提交于
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
-
- 23 3月, 2000 14 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
allow to write applications which do not have a link to postgres_ext.h in their source directory. Andreas Kardos
-
由 Michael Meskes 提交于
-
由 Tom Lane 提交于
cases but actually did no such thing. Make it test some more cases than before (including things that didn't work in 6.5).
-
由 Tom Lane 提交于
input, not throw a gratuitous elog().
-
由 Tom Lane 提交于
outside WHERE clause. Fix a couple of places that didn't handle uplevel refs cleanly.
-
由 Tom Lane 提交于
nodes introduced by make_subplan(). It'd be better if we used a different node type for subplan result placeholders, but for now...
-
由 Tom Lane 提交于
Const placeholder nodes for subplan result values.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
-
由 Tom Lane 提交于
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.
-
由 Tom Lane 提交于
to more than one character, and try to do the right thing in non-ASCII locales.
-
由 Tom Lane 提交于
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.
-
- 22 3月, 2000 1 次提交
-
-
由 Bruce Momjian 提交于
-