summaryrefslogtreecommitdiff
path: root/src/test
Commit message (Collapse)AuthorAgeFilesLines
* Update this branch to match CVS head, includes WIN32 improvements.Bruce Momjian2003-09-0721-63/+111
|
* create_unique_plan() should not discard existing output columns of theTom Lane2003-08-072-0/+20
| | | | | | subplan it starts with, as they may be needed at upper join levels. See comments added to code for the non-obvious reason why. Per bug report from Robert Creager.
* Remove unnecessary use of multiple cat processes to feed psql; thisTom Lane2003-08-071-13/+4
| | | | | | | reduces the number of concurrent processes launched during parallel regression tests, possibly avoiding failures such as exceeding a user's max number of processes. This essentially completes the reversion of 1.27->1.28.
* HPUX's horology behavior is OS-dependent, not hardware-dependent.Tom Lane2003-08-041-1/+1
|
* Update copyrights to 2003.Bruce Momjian2003-08-041-2/+2
|
* pgindent run.Bruce Momjian2003-08-044-26/+27
|
* Adjust 'permission denied' messages to be more useful and consistent.Tom Lane2003-08-012-33/+33
|
* When using a temp installation, unset PGUSER and other variables weTom Lane2003-07-311-1/+5
| | | | | | might have inherited from the environment that would possibly cause psql to fail to connect to the temp installation properly. Per trouble report from Markus Bertheau 7/1/03.
* When shutting down the regression test postmaster after 'make check',Tom Lane2003-07-301-1/+2
| | | | | | wait for the postmaster to actually exit. Otherwise running repeated 'make check's tends to misbehave, because we try to remove and recreate the data directory while the old PM is still alive.
* Apply (a somewhat revised version of) Greg Mullane's patch to eliminateTom Lane2003-07-299-65/+92
| | | | | | | | | heuristic determination of day vs month in date/time input. Add the ability to specify that input is interpreted as yy-mm-dd order (which formerly worked, but only for yy greater than 31). DateStyle's input component now has the preferred spellings DMY, MDY, or YMD; the older keywords European and US are now aliases for the first two of these. Per recent discussions on pgsql-general.
* A visit from the message-style police ...Tom Lane2003-07-284-6/+6
|
* elog mop-up: bring some straggling fprintf(stderr)'s into the elog world.Tom Lane2003-07-271-6/+2
|
* Fix some localizability issues with existing errcontext() calls.Tom Lane2003-07-271-4/+4
|
* Error message editing in utils/adt. Again thanks to Joe Conway for doingTom Lane2003-07-2735-126/+133
| | | | the bulk of the heavy lifting ...
* > Joe Conway <mail@joeconway.com> writes:Bruce Momjian2003-07-273-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | >>ISTM that "source" is worth knowing. > > Hm, possibly. Any other opinions? This version has the seven fields I proposed, including "source". Here's an example that shows why I think it's valuable: regression=# \x Expanded display is on. regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | on context | user vartype | bool source | default min_val | max_val | regression=# update pg_settings set setting = 'off' where name = 'enable_seqscan'; -[ RECORD 1 ]--- set_config | off regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | off context | user vartype | bool source | session min_val | max_val | regression=# alter user postgres set enable_seqscan to 'off'; ALTER USER (log out and then back in again) regression=# \x Expanded display is on. regression=# select * from pg_settings where name = 'enable_seqscan'; -[ RECORD 1 ]----------- name | enable_seqscan setting | off context | user vartype | bool source | user min_val | max_val | In the first case, enable_seqscan is set to its default value. After setting it to off, it is obvious that the value has been changed for the session only. In the third case, you can see that the value has been set specifically for the user. Joe Conway
* The deferred trigger queue pushing to disk patch pointed outBruce Momjian2003-07-272-0/+39
| | | | | | | | | | that the regression tests for foreign keys didn't seem to test a deferred constraint that was not satisified by a later statement and was not made immediate by set constraints, so here's a simple added test with a single invalid insert and a commit. Stephan Szabo
* Error message editing in backend/utils (except /adt).Tom Lane2003-07-251-2/+4
|
* Error message editing in contrib (mostly by Joe Conway --- thanks Joe!)Tom Lane2003-07-241-5/+8
|
* Error message editing for foreign-key triggers.Tom Lane2003-07-223-33/+66
|
* Error message editing in backend/libpq, backend/postmaster, backend/tcop.Tom Lane2003-07-221-2/+2
| | | | | Along the way, fix some logic problems in pgstat_initstats, notably the bogus assumption that malloc returns zeroed memory.
* Don't report sequendces in pg_tables.Bruce Momjian2003-07-221-1/+1
|
* Error message editing in backend/access.Tom Lane2003-07-216-16/+16
|
* Fix regression test broken by recent view change.Tom Lane2003-07-211-1/+1
|
* Error message editing in backend/executor.Tom Lane2003-07-216-59/+59
|
* Error message editing in backend/catalog.Tom Lane2003-07-219-85/+103
|
* Another round of error message editing, covering backend/commands/.Tom Lane2003-07-2013-121/+122
|
* Another round of error message editing, covering backend/parser/.Tom Lane2003-07-1924-158/+160
|
* First bits of work on error message editing.Tom Lane2003-07-184-18/+24
|
* It seems some case-insensitive locales sort upper case before lowerTom Lane2003-07-183-5/+381
| | | | | (BBBB before bbbb) and others the other way around. Provide comparison files that cater to both approaches.
* Cause SHOW DATESTYLE to produce a string that will be accepted by SETTom Lane2003-07-153-45/+45
| | | | | | DATESTYLE, for instance 'SQL, European' instead of 'SQL with European conventions'. Per gripe a month or two back from Barry Lind.
* Some early work on error message editing. Operator-not-found andTom Lane2003-07-0412-109/+109
| | | | | function-not-found messages now distinguish the cases no-match and ambiguous-match, and they follow the style guidelines too.
* Aggregates can be polymorphic, using polymorphic implementation functions.Tom Lane2003-07-014-2/+884
| | | | | | It also works to create a non-polymorphic aggregate from polymorphic functions, should you want to do that. Regression test added, docs still lacking. By Joe Conway, with some kibitzing from Tom Lane.
* Change EXECUTE INTO to CREATE TABLE AS EXECUTE.Peter Eisentraut2003-07-012-4/+4
|
* Support expressions of the form 'scalar op ANY (array)' andTom Lane2003-06-292-0/+78
| | | | | | | | | | 'scalar op ALL (array)', where the operator is applied between the lefthand scalar and each element of the array. The operator must yield boolean; the result of the construct is the OR or AND of the per-element results, respectively. Original coding by Joe Conway, after an idea of Peter's. Rewritten by Tom to keep the implementation strictly separate from subqueries.
* Create real array comparison functions (that use the element datatype'sTom Lane2003-06-272-32/+39
| | | | | | | | | | | | | | | | comparison functions), replacing the highly bogus bitwise array_eq. Create a btree index opclass for ANYARRAY --- it is now possible to create indexes on array columns. Arrange to cache the results of catalog lookups across multiple array operations, instead of repeating the lookups on every call. Add string_to_array and array_to_string functions. Remove singleton_array, array_accum, array_assign, and array_subscript functions, since these were for proof-of-concept and not intended to become supported functions. Minor adjustments to behavior in some corner cases with empty or zero-dimensional arrays. Joe Conway (with some editorializing by Tom Lane).
* Back out array mega-patch.Bruce Momjian2003-06-252-4/+32
| | | | Joe Conway
* In ISO datestyle, never emit just HH:MM, always emit HH:MM:SS orTom Lane2003-06-251-78/+78
| | | | | | | | HH:MM:SS.SSS... when there is a nonzero part-of-a-day field in an interval value. The seconds part used to be suppressed if zero, but there's no equivalent behavior for timestamp, and since we're modeling this format on timestamp it's probably wrong. Per complaint and patch from Larry Rosenman.
* Includes:Bruce Momjian2003-06-253-1/+70
| | | | | | | | | | | | | | | | - LIKE <subtable> [ INCLUDING DEFAULTS | EXCLUDING DEFAULTS ] - Quick cleanup of analyze.c function prototypes. - New non-reserved keywords (INCLUDING, EXCLUDING, DEFAULTS), SQL 200X Opted not to extend for check constraints at this time. As per the definition that it's user defined columns, OIDs are NOT inherited. Doc and Source patches attached. -- Rod Taylor <rbt@rbt.ca>
* Back out commit.Bruce Momjian2003-06-251-43/+0
|
* Adjust expected output for new functions.Bruce Momjian2003-06-251-0/+43
|
* Array mega-patch.Bruce Momjian2003-06-242-32/+4
| | | | Joe Conway
* Add ipv6 address parsing support to 'inet' and 'cidr' data types.Bruce Momjian2003-06-242-106/+138
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Regression tests for IPv6 operations added. Documentation updated to document IPv6 bits. Stop treating IPv4 as an "unsigned int" and IPv6 as an array of characters. Instead, always use the array of characters so we can have one function fits all. This makes bitncmp(), addressOK(), and several other functions "just work" on both address families. add family() function which returns integer 4 or 6 for IPv4 or IPv6. (See examples below) Note that to add this new function you will need to dump/initdb/reload or find the correct magic to add the function to the postgresql function catalogs. IPv4 addresses always sort before IPv6. On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses. This prevents the need for a dump and reload, but lets IPv6 parsing work on machines without AF_INET6. To select all IPv4 addresses from a table: select * from foo where family(addr) = 4 ... Order by and other bits should all work. Michael Graff
* Revise hash join and hash aggregation code to use the same datatype-Tom Lane2003-06-222-9/+62
| | | | | | | | specific hash functions used by hash indexes, rather than the old not-datatype-aware ComputeHashFunc routine. This makes it safe to do hash joining on several datatypes that previously couldn't use hashing. The sets of datatypes that are hash indexable and hash joinable are now exactly the same, whereas before each had some that weren't in the other.
* Bring the libpq example programs into the 21st century.Tom Lane2003-06-227-244/+218
|
* Okay, recognize freebsd 2.* and 3.* too.Tom Lane2003-06-131-1/+1
|
* Expect FreeBSD 5.* to have standard float arithmetic.Tom Lane2003-06-131-1/+1
|
* Implement outer-level aggregates to conform to the SQL spec, withTom Lane2003-06-062-0/+33
| | | | | | | | extensions to support our historical behavior. An aggregate belongs to the closest query level of any of the variables in its argument, or the current query level if there are no variables (e.g., COUNT(*)). The implementation involves adding an agglevelsup field to Aggref, and treating outer aggregates like outer variables at planning time.
* Adopt latest bison's spelling of 'syntax error' rather than 'parse error'Tom Lane2003-05-294-32/+32
| | | | | for grammar-detected problems. Revert Makefile hack that kept it looking like the pre-bison-1.875 output.
* Add a regression test to catch future silliness in the index-buildingTom Lane2003-05-292-0/+15
| | | | area...
* Replace functional-index facility with expressional indexes. Any columnTom Lane2003-05-284-2/+32
| | | | | | | | | | | of an index can now be a computed expression instead of a simple variable. Restrictions on expressions are the same as for predicates (only immutable functions, no sub-selects). This fixes problems recently introduced with inlining SQL functions, because the inlining transformation is applied to both expression trees so the planner can still match them up. Along the way, improve efficiency of handling index predicates (both predicates and index expressions are now cached by the relcache) and fix 7.3 oversight that didn't record dependencies of predicate expressions.
View Lorry Controller Status