aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* A little further tweaking of the range-query selectivity logic:Tom Lane2000-03-23
| | | | | | | 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.
* >> 5. empty define that results in an empty but terminated line ( ; )Bruce Momjian2000-03-23
| | | | | | easy (maybe dumb) fix for 5 in attachment define.patch greetings, Andreas
* Back out // compiler flag.Bruce Momjian2000-03-23
|
* Hmm, absolute pathnames for the copy makes sense. I'll whip up thatBruce Momjian2000-03-23
| | | | | | | patch in a second. Should be sufficent to just make sure the first character is a '/', right? Ross J. Reedstrom
* Some points for portability improvements:Bruce Momjian2000-03-23
| | | | | | | | | | | | | | | | | | | 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
* Please apply the attached patch to interfaces/libpq/libpq-fe.h. This wouldBruce Momjian2000-03-23
| | | | | | | allow to write applications which do not have a link to postgres_ext.h in their source directory. Andreas Kardos
* *** empty log message ***Michael Meskes2000-03-23
|
* subselect regress test was kind of silly; it claimed to test correlationTom Lane2000-03-23
| | | | | cases but actually did no such thing. Make it test some more cases than before (including things that didn't work in 6.5).
* Float-to-int conversion functions should return NULL when given NULLTom Lane2000-03-23
| | | | input, not throw a gratuitous elog().
* Remove no-longer-necessary restriction against uplevel correlation varsTom Lane2000-03-23
| | | | | outside WHERE clause. Fix a couple of places that didn't handle uplevel refs cleanly.
* Hack parse_coerce so it won't try to constant-fold the dummy ConstTom Lane2000-03-23
| | | | | nodes introduced by make_subplan(). It'd be better if we used a different node type for subplan result placeholders, but for now...
* ExecSubPlan needs to be able to cope with RelabelType nodes atop theTom Lane2000-03-23
| | | | Const placeholder nodes for subplan result values.
* Update HISTORY file for 7.0.Bruce Momjian2000-03-23
|
* If we cannot get a real estimate for the selectivity of a range query,Tom Lane2000-03-23
| | | | | | 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.
* Improve selectivity estimation involving string constants: pay attentionTom Lane2000-03-23
| | | | | to more than one character, and try to do the right thing in non-ASCII locales.
* Repair logic flaw in cost estimator: cost_nestloop() was estimating CPUTom Lane2000-03-22
| | | | | | | | | | | | | 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 pg_dumpall again.Bruce Momjian2000-03-22
|
* Fix pg_dumpall for new psql output.Bruce Momjian2000-03-22
|
* Forgot that odbc had its own copies of config.sub/config.guess.Tom Lane2000-03-21
| | | | Update those to latest Autoconf sources, too.
* Fix query for primary keys to reflect new DISTINCT ON () syntax.Thomas G. Lockhart2000-03-21
| | | | | Reported by "Tibor Laszlo" <ltibor@mail.tiszanet.hu> and fix suggested by "Hiroshi Inoue" <Inoue@tpf.co.jp>.
* Add syntax for BIT() and BIT VARYING(), but no underlying implementationThomas G. Lockhart2000-03-21
| | | | | | is available yet. Remove redundant call to xlateSqlType() in the character type handling code.
* Update test for new ORDER BY clause from Tom Lane.Thomas G. Lockhart2000-03-21
|
* Restructure planning code so that preprocessing of targetlist and qualsTom Lane2000-03-21
| | | | | | | | | | | | | 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.
* Correct typo in error message.Tom Lane2000-03-21
|
* Reverse out BYTEA type coersion.Bruce Momjian2000-03-20
|
* Turn XLOG off (do not create log file).Vadim B. Mikheev2000-03-20
|
* Emit 'this operator is deprecated' warnings for ':' and ';'.Tom Lane2000-03-20
|
* Convert float8 regress test to use exp() and ln() instead of ':' andTom Lane2000-03-20
| | | | ';' operators.
* Update for BYTEAOID.Bruce Momjian2000-03-20
|
* Add compatiblity information for bytea.Bruce Momjian2000-03-20
|
* Add FORCE keyword to ColIDHiroshi Inoue2000-03-20
|
* Make use of pre-existing regexp match capability to eliminate redundantTom Lane2000-03-19
| | | | | entries in template selection rules. Also, change alpha-dec-osf pattern to cope with version info attached to the 'alpha' part.
* Autoconf runTom Lane2000-03-19
|
* Change configure.in to note that since we are using expr(1)'s regex matchTom Lane2000-03-19
| | | | | | 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.
* cash_words_out function truncated its output by 1 character due toTom Lane2000-03-19
| | | | incorrect use of StrNCpy.
* Several calls to StrNCpy incorrectly subtracted 1 from the length arg,Tom Lane2000-03-19
| | | | leading to postmaster accepting args 1 shorter than it had room for.
* Change MemSet and StrNCpy to evaluate their arguments only once.Tom Lane2000-03-19
| | | | Fix inadequate parenthesization in several other macros.
* Proper unpack de_DE.ISO-8859-1Bruce Momjian2000-03-19
|
* Minor code rearrangement & doc improvement in eval_const_expressions().Tom Lane2000-03-19
|
* *** empty log message ***Michael Meskes2000-03-19
|
* transformExpr() did the Wrong Thing if applied to a SubLink node thatTom Lane2000-03-19
| | | | | | | | | 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.
* it seems in the beta2 release DBUSERID in pg_dumpall is the _name_ of theBruce Momjian2000-03-19
| | | | | | | | | | | | | 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
* Fix incorrect implementation of log(x) for numeric, as well asTom Lane2000-03-19
| | | | | | 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...
* Another go-round with resolution of ambiguous functions and operators.Tom Lane2000-03-19
| | | | | | | | | | 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.
* In can_coerce_type, verify that a possible type-coercion functionTom Lane2000-03-19
| | | | actually returns the type it is named for.
* Fixed psql -c "\slashcmd"Peter Eisentraut2000-03-18
|
* Update bytea type descriptionBruce Momjian2000-03-18
|
* Improve error message wording in unary_op_error() --- suggest thatTom Lane2000-03-18
| | | | | | 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).
* Clean up minor compiler warnings.Tom Lane2000-03-18
|
* Modify lexing of multi-char operators per pghackers discussion aroundTom Lane2000-03-18
| | | | | | | | | | 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.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 09:23:19 +0000