aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Updated user's guide to match new psql's output formatPeter Eisentraut2000-03-26
| | | | Fixed bug in createdb/alternative location
* Change resultmap:Tatsuo Ishii2000-03-26
| | | | | powerpc-unknown-linux-gnu --> powerpc-unknown-linux-gnulibc1 this is because for new config.guess.
* New platform specific geometry regression expected file forTatsuo Ishii2000-03-26
| | | | powerpc-linux-gnulibc1.
* Remove some results from int4-not-representable.outTatsuo Ishii2000-03-26
| | | | | | | | | | | | | | | | | | | | | | | 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) <
* Make configure --help produce slightly more useful and consistently-Tom Lane2000-03-26
| | | | formatted descriptions of --with options.
* Attached is the regression diff for geometry, RedHat 6.1 on a PentiumBruce Momjian2000-03-26
| | | | | | | | 200 MMX. I was going through my e-mail, cleaning out my 1000+ message inbox, and found this one. Sorry. -- Lamar Owen
* Remove bogus complexity from build/install of plperl. This stuff wasTom Lane2000-03-25
| | | | | | 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.
* Old patch from Mark Hollomon to add plperl to createlang's repertoire.Tom Lane2000-03-25
| | | | Seems to have slipped through the cracks.
* Another fix for old shells.Tom Lane2000-03-25
|
* Fix syntax error reported by old shells ("if ! command..." is aTom Lane2000-03-25
| | | | neologism, apparently).
* More >&1 cleanupsBruce Momjian2000-03-25
|
* More changes of >& to 2>&1Bruce Momjian2000-03-25
|
* Remove >& and make it 2>&1Bruce Momjian2000-03-25
|
* Add POLLUTE=1 to perl Makefile.PL creations.Bruce Momjian2000-03-25
|
* transformCreateStmt should put Ident nodes, not ColumnDef nodes, intoTom Lane2000-03-24
| | | | | | | | | | | | | | | | | 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)
* Improve comment.Tom Lane2000-03-24
|
* Save a few cycles in simple cases: no need to call cost_sort() when thereTom Lane2000-03-24
| | | | is no presorted path to compare with.
* Remove -O2 for aix.Bruce Momjian2000-03-24
|
* outfuncs.c was missing a print routine for Material plan nodes, leadingTom Lane2000-03-24
| | | | to trouble when trying to EXPLAIN VERBOSE a plan containing one.
* Rename bytea functions to not have upper-case letters in their names.Tom Lane2000-03-24
| | | | | | 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...
* Fold PQsetenv working state into PGconn, rather than trying to maintainTom Lane2000-03-24
| | | | | | | | 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.
* 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
|