summaryrefslogtreecommitdiff
path: root/src/test
Commit message (Collapse)AuthorAgeFilesLines
* Fix for char_length() changesTatsuo Ishii2000-03-161-5/+5
|
* Tweak GROUP BY so that it will still accept result-column names, but onlyTom Lane2000-03-152-7/+10
| | | | | | | | | | after trying to resolve the item as an input-column name. This allows us to be compliant with the SQL92 spec for queries that fall within the spec, while still accepting the same out-of-spec queries as 6.5 did. You'll only lose if there is an output column name that is the same as an input column name, but doesn't refer to the same value. 7.0 will interpret such a GROUP BY spec differently than 6.5 did. No way around that, because 6.5 was clearly not spec compliant.
* Fix a couple of missed changes in expected results.Tom Lane2000-03-152-20/+2
|
* Implement column aliases on views "CREATE VIEW name (collist)".Thomas G. Lockhart2000-03-1417-132/+144
| | | | | | | | | | | | | | | | | | Implement TIME WITH TIME ZONE type (timetz internal type). Remap length() for character strings to CHAR_LENGTH() for SQL92 and to remove the ambiguity with geometric length() functions. Keep length() for character strings for backward compatibility. Shrink stored views by removing internal column name list from visible rte. Implement min(), max() for time and timetz data types. Implement conversion of TIME to INTERVAL. Implement abs(), mod(), fac() for the int8 data type. Rename some math functions to generic names: round(), sqrt(), cbrt(), pow(), etc. Rename NUMERIC power() function to pow(). Fix int2 factorial to calculate result in int4. Enhance the Oracle compatibility function translate() to work with string arguments (from Edwin Ramirez). Modify pg_proc system table to remove OID holes.
* > Here is an extension of the regression test suite for Digital UnixBruce Momjian2000-03-141-0/+246
| | | | | | (Alpha). > > Andreas Kardos
* > Here is an extension of the regression test suite for Digital UnixBruce Momjian2000-03-141-0/+3
| | | | | (Alpha). >
* Remove SHOW after datestyle reset.Bruce Momjian2000-03-094-9/+0
|
* Hi,Bruce Momjian2000-03-081-1/+0
| | | | | | | | | The regression test script runcheck.sh doesn't seem able to handle the blank line on the end of the resultmap file. Here's a patch to remove it!! Keith.
* Hi,Bruce Momjian2000-03-086-0/+1318
| | | | | | | | | | | | | the to_char() source code is large, here are regression tests for numeric/timestamp/int8 part. It is probably enough test for formatting code in the formatting.c module. The others (float4/float8/int4) types share this formatting code and eventual bugs for these types aren't few probable. Patch fix timestamp_to_char() for infinity/invalid timestamp too. Karel
* Add SQL_ASCII encoding test caseTatsuo Ishii2000-03-061-0/+19
|
* More fixes for psql ^C handling, especially during copy. Still doesn'tPeter Eisentraut2000-03-012-4/+4
| | | | | | cope so well with copy to but that will have to wait for the next release. Also added -X option to prevent reading .psqlrc startup file.
* Add QNX fixes from Kardos, Dr. AndreasBruce Momjian2000-03-015-7/+526
|
* remove extra include.Bruce Momjian2000-02-281-1/+0
|
* Update expected files due to the psql format changeTatsuo Ishii2000-02-278-604/+604
|
* Suppress unneccesary message from createdbTatsuo Ishii2000-02-271-2/+2
|
* Add SQL_ASCII test caseTatsuo Ishii2000-02-271-0/+87
|
* Fix multibyte regress results for EUC_CN, EUC_KR and EUC_TWTatsuo Ishii2000-02-273-190/+190
|
* Add LinuxPPC mappingsTatsuo Ishii2000-02-271-0/+3
|
* Enabled regression driver to run without PGLIB set.Peter Eisentraut2000-02-241-3/+3
|
* Add missing files like foreign key regression tests and config.h.win32.Bruce Momjian2000-02-242-0/+1106
|
* 1. miscadmin.h needs to include sys/types.h for a definition of pid_tBruce Momjian2000-02-231-0/+5
| | | | | | | | | | | | 2. Regression tests fail for types int2 and int4 (which can easily be fixed by adding entries to resultmap) aswell as float8 and geometry, where floating point numbers appear to be rounded a little differently than in your expected results (besides that I also need the positive zeros file). I'm including a patch for the first 2, but I don't know whether the latter two are actually a bug in postgres or a bug in the OS or even allowed difference. I'm including my results for reference. Rolf Grossmann
* Well, here's the first pass on regressionBruce Momjian2000-02-223-0/+55
| | | | | | | | | | | | | | | tests for the Foreign Key support in 7.0 which was made against a CVS copy from this afternoon. This modifies src/test/regress/sql/run_check.tests src/test/regress/sql/alter_table.sql src/test/regress/expected/alter_table.out src/test/regress/sql/foreign_key.sql src/test/regress/expected/foreign_key.out sszabo@bigpanda.co
* Quick hack solution so that pg_dump of views works. Needs repair afterTom Lane2000-02-211-8/+8
| | | | Thomas gets back, but better this than nonfunctional pg_dump in the beta.
* To avoid confusion during early beta testing, commit the current rulesTom Lane2000-02-211-26/+26
| | | | | test output as expected output. We'll probably want to change this again after something's done about the verbosity of column alias display.
* Add a simple regress test for SERIAL --- it's not much,Tom Lane2000-02-204-2/+37
| | | | but it's better than no test at all...
* Repair longstanding violation of SQL92 semantics: GROUP BY wouldTom Lane2000-02-192-18/+23
| | | | | | | | | | | | | | interpret a column name as an output column alias (targetlist AS name), ather than a real column name as it ought to. According to the spec, only ORDER BY should look at output column names. I left in GROUP BY's willingness to use an output column number ('GROUP BY 2'), even though this is also contrary to the spec --- again, only ORDER BY is supposed to accept that. But there is no possible reason to want to GROUP BY an integer constant, so keeping this old behavior won't break any SQL-compliant queries. DISTINCT ON will behave the same as GROUP BY. Change numerology regress test, which depended on the incorrect behavior.
* Apply Keith Park's updates for expected/horology-solaris-1947.out. FixTom Lane2000-02-194-936/+486
| | | | | | erroneous expected output for RESET DateStyle: should be ISO now. Fix run_check.sh so that test postmaster is started with PGDATESTYLE=ISO, else the horology test won't pass.
* Finish repairing 6.5's problems with r-tree indexes: create appropriateTom Lane2000-02-172-2/+20
| | | | | | | | | | | | selectivity functions and make the r-tree operators use them. The estimation functions themselves are just stubs, unfortunately, but perhaps someday someone will make them compute realistic estimates. Change pg_am so that the optimizer can reliably tell the difference between ordered and unordered indexes --- before it would think that an r-tree index can be scanned in '<<' order, which is not right AFAIK. Repair broken negator links for network_sup and related ops. Initdb forced. This might be my last initdb force for 7.0 ... hope so anyway ...
* Update expected/horology-no-DST-before-1970.out to matchTom Lane2000-02-171-930/+470
| | | | | new datetime regress test. Someone needs to deal with fixing expected/horology-solaris-1947.out too, assuming we still need it.
* All regression tests pass except for rules.sql (unrelated).Thomas G. Lockhart2000-02-1611-1410/+909
| | | | | | | | | | | | | | Implement "date/time grand unification". Transform datetime and timespan into timestamp and interval. Deprecate datetime and timespan, though translate to new types in gram.y. Transform all datetime and timespan catalog entries into new types. Make "INTERVAL" reserved word allowed as a column identifier in gram.y. Remove dt.h, dt.c files, and retarget datetime.h, datetime.c as utility routines for all date/time types. date.{h,c} now deals with date, time types. timestamp.{h,c} now deals with timestamp, interval types. nabstime.{h,c} now deals with abstime, reltime, tinterval types. Make NUMERIC a known native type for purposes of type coersion. Not tested.
* New cost model for planning, incorporating a penalty for random pageTom Lane2000-02-154-4/+13
| | | | | | | | | | | | | | | | | | | | | | | | | accesses versus sequential accesses, a (very crude) estimate of the effects of caching on random page accesses, and cost to evaluate WHERE- clause expressions. Export critical parameters for this model as SET variables. Also, create SET variables for the planner's enable flags (enable_seqscan, enable_indexscan, etc) so that these can be controlled more conveniently than via PGOPTIONS. Planner now estimates both startup cost (cost before retrieving first tuple) and total cost of each path, so it can optimize queries with LIMIT on a reasonable basis by interpolating between these costs. Same facility is a win for EXISTS(...) subqueries and some other cases. Redesign pathkey representation to achieve a major speedup in planning (I saw as much as 5X on a 10-way join); also minor changes in planner to reduce memory consumption by recycling discarded Path nodes and not constructing unnecessary lists. Minor cleanups to display more-plausible costs in some cases in EXPLAIN output. Initdb forced by change in interface to index cost estimation functions.
* Change to report COPY line number in error messages affectsTom Lane2000-02-151-1/+1
| | | | results of constraints regress test.
* Update "join syntax" test for new capabilities.Thomas G. Lockhart2000-02-152-76/+312
|
* Add line to mention PST8PDT time zone. Seems useful, but maybe not?Thomas G. Lockhart2000-02-151-1/+2
|
* Fix up error message to start with cap letter.Thomas G. Lockhart2000-02-151-4/+4
|
* Adjusted psql echoing options (-a and -e)Peter Eisentraut2000-02-132-4/+4
|
* Solaris has always had problems with 1947 in theBruce Momjian2000-02-0621-508/+2965
| | | | | | | | | | | | | | regression tests so I prepared a set of expected files to make things look OK. There's also a file to account for minor variations in the geopmetry output and a resultmap patch to pull them all together. With these changes PostgreSQL, from CVS, builds and regression tests (runcheck) cleanly. Keith Parks.
* A few minor psql enhancementsPeter Eisentraut2000-01-291-2/+2
| | | | | | | Initdb help correction Changed end/abort to commit/rollback and changed related notices Commented out way old printing functions in libpq Fixed a typo in alter table / alter column
* Redesign DISTINCT ON as discussed in pgsql-sql 1/25/00: syntax is nowTom Lane2000-01-274-24/+80
| | | | | | | | | | | | | SELECT DISTINCT ON (expr [, expr ...]) targetlist ... and there is a check to make sure that the user didn't specify an ORDER BY that's incompatible with the DISTINCT operation. Reimplement nodeUnique and nodeGroup to use the proper datatype-specific equality function for each column being compared --- they used to do bitwise comparisons or convert the data to text strings and strcmp(). (To add insult to injury, they'd look up the conversion functions once for each tuple...) Parse/plan representation of DISTINCT is now a list of SortClause nodes. initdb forced by querytree change...
* Add:Bruce Momjian2000-01-262-4/+6
| | | | | | * Portions Copyright (c) 1996-2000, PostgreSQL, Inc to all files copyright Regents of Berkeley. Man, that's a lot of files.
* Forgot that expr assumes regexp is anchored-left; therefore need .*Tom Lane2000-01-251-3/+3
| | | | | in front of any platform name pattern that's not supposed to match beginning at the start of the machine type name...
* Update regress tests for change of pg_am/pg_amop.Tom Lane2000-01-223-447/+448
|
* Revise handling of index-type-specific indexscan cost estimation, perTom Lane2000-01-221-31/+4
| | | | | | pghackers discussion of 5-Jan-2000. The amopselect and amopnpages estimators are gone, and in their place is a per-AM amcostestimate procedure (linked to from pg_am, not pg_amop).
* Simplify match patterns a little.Tom Lane2000-01-211-5/+4
|
* Bruce, you forgot to rename these files...Tom Lane2000-01-212-532/+0
|
* I have noticed that the geometry test's output for hppa1 and hppa2 are inBruce Momjian2000-01-201-2/+5
| | | | | | | | | | | | | | | | | fact the same, so I suggest they could be the same file say geometry-positive-zeros.out, as the main difference seems to be not printing eg. (0,-0). In src/test/regress/expected, I propose rm int2-i386-netbsd.out int4-i386-netbsd.out mv geometry-hppa1.1.out geometry-positive-zeros.out rm geometry-hppa2.0.out geometry-i386-netbsd.out and the following patch to resultmap. I have only tested the netbsd results on i386, but think that in all probability the differences will be the same for other ports. If it turns out not to be the case, at least we might find out. Patrick Welche
* Fix handling of NULL constraint conditions: per SQL92 spec, a NULL resultTom Lane2000-01-192-10/+30
| | | | | | | | | from a constraint condition does not violate the constraint (cf. discussion on pghackers 12/9/99). Implemented by adding a parameter to ExecQual, specifying whether to return TRUE or FALSE when the qual result is really NULL in three-valued boolean logic. Currently, ExecRelCheck is the only caller that asks for TRUE, but if we find any other places that have the wrong response to NULL, it'll be easy to fix them.
* Adopt for new psqlTatsuo Ishii2000-01-182-129/+129
|
* Update strings test to reflect the fact that casting to char() willTom Lane2000-01-172-18/+18
| | | | now truncate or pad to the specified length.
* Included all yacc and lex files into the distribution.Peter Eisentraut2000-01-161-1/+13
|
View Lorry Controller Status