summaryrefslogtreecommitdiff
path: root/src/test/regress
Commit message (Collapse)AuthorAgeFilesLines
* Message style improvementsPeter Eisentraut2006-10-063-3/+3
|
* pgindent run for 8.2.Bruce Momjian2006-10-041-144/+149
|
* Improve numeric overflow error message.Bruce Momjian2006-10-031-2/+2
| | | | David Fetter
* Allow assignment to array elements not contiguous with those alreadyTom Lane2006-09-292-0/+146
| | | | | | | | | | present; intervening positions are filled with nulls. This behavior is required by SQL99 but was not implementable before 8.2 due to lack of support for nulls in arrays. I have only made it work for the one-dimensional case, which is all that SQL99 requires. It seems quite complex to get it right in higher dimensions, and since we never allowed extension at all in higher dimensions, I think that must count as a future feature addition not a bug fix.
* Cause pg_regress to invoke the temporary postmaster as 'postgres' notTom Lane2006-09-241-8/+10
| | | | | | 'postmaster', so as not to depend on the existence of the postmaster symlink. Also, implement postmaster-still-alive and postmaster-kill operations for Windows, per Magnus.
* Fix shared library creation to work properly on AIX. Albe LaurenzTom Lane2006-09-191-4/+6
|
* Rename the recently-added pg_timezonenames view to pg_timezone_abbrevs,Tom Lane2006-09-161-2/+3
| | | | | | and create a new view pg_timezone_names that provides information about the zones known in the 'zic' database. Magnus Hagander, with some additional work by Tom Lane.
* Rename contains/contained-by operators to @> and <@, per discussion thatTom Lane2006-09-1016-99/+103
| | | | | | | | agreed these symbols are less easily confused. I made new pg_operator entries (with new OIDs) for the old names, so as to provide backward compatibility while making it pretty easy to remove the old names in some future release cycle. This commit only touches the core datatypes, contrib will be fixed separately.
* Add interval division/multiplication regression tests.Bruce Momjian2006-09-062-0/+101
| | | | Michael Glaesemann
* Get rid of the separate RULE privilege for tables: now only a table's ownerTom Lane2006-09-053-29/+15
| | | | | | | | | | | | | can create or modify rules for the table. Do setRuleCheckAsUser() while loading rules into the relcache, rather than when defining a rule. This ensures that permission checks for tables referenced in a rule are done with respect to the current owner of the rule's table, whereas formerly ALTER TABLE OWNER would fail to update the permission checking for associated rules. Removal of separate RULE privilege is needed to prevent various scenarios in which a grantee of RULE privilege could effectively have any privilege of the table owner. For backwards compatibility, GRANT/REVOKE RULE is still accepted, but it doesn't do anything. Per discussion here: http://archives.postgresql.org/pgsql-hackers/2006-04/msg01138.php
* Fix interval input parser so that fractional weeks and months areTom Lane2006-09-042-0/+14
| | | | | | | cascaded first to days and only what is leftover into seconds. This seems to satisfy the principle of least surprise given the general conversion to three-part interval values --- it was an oversight that these cases weren't dealt with in 8.1. Michael Glaesemann
* Code review for UPDATE SET (columnlist) patch. Make it handle as muchTom Lane2006-09-032-30/+75
| | | | | | of the syntax as this fundamentally dead-end approach can, in particular combinations of single and multi column assignments. Improve rather inadequate documentation and provide some regression tests.
* Properly round months into days and into seconds for intervalBruce Momjian2006-09-031-1/+1
| | | | | | | multiplication/division queries like select '41 mon 10:00:00'::interval / 10 as "pos". Report from Michael Glaesemann
* Apply a simple solution to the problem of making INSERT/UPDATE/DELETETom Lane2006-09-022-2/+210
| | | | | | | | | | | | | | | RETURNING play nice with views/rules. To wit, have the rule rewriter rewrite any RETURNING clause found in a rule to produce what the rule's triggering query asked for in its RETURNING clause, in particular drop the RETURNING clause if no RETURNING in the triggering query. This leaves the responsibility for knowing how to produce the view's output columns on the rule author, without requiring any fundamental changes in rule semantics such as adding new rule event types would do. The initial implementation constrains things to ensure that there is exactly one, unconditionally invoked RETURNING clause among the rules for an event --- later we might be able to relax that, but for a post feature freeze fix it seems better to minimize how much invention we do. Per gripe from Jaime Casanova.
* Extend COPY to support COPY (SELECT ...) TO ...Tom Lane2006-08-304-3/+212
| | | | Bernd Helmle
* Add the ability to create indexes 'concurrently', that is, withoutTom Lane2006-08-252-0/+90
| | | | | blocking concurrent writes to the table. Greg Stark, with a little help from Tom Lane.
* Fix all known problems with pg_dump's handling of serial sequencesTom Lane2006-08-215-5/+20
| | | | | | | | | | | | | | | | | | | | | by abandoning the idea that it should say SERIAL in the dump. Instead, dump serial sequences and column defaults just like regular ones. Add a new backend command ALTER SEQUENCE OWNED BY to let pg_dump recreate the sequence-to-column dependency that was formerly created "behind the scenes" by SERIAL. This restores SERIAL to being truly "just a macro" consisting of component operations that can be stated explicitly in SQL. Furthermore, the new command allows sequence ownership to be reassigned, so that old mistakes can be cleaned up. Also, downgrade the OWNED-BY dependency from INTERNAL to AUTO, since there is no longer any very compelling argument why the sequence couldn't be dropped while keeping the column. (This forces initdb, to be sure the right kinds of dependencies are in there.) Along the way, add checks to prevent ALTER OWNER or SET SCHEMA on an owned sequence; you can now only do this indirectly by changing the owning table's owner or schema. This is an oversight in previous releases, but probably not worth back-patching.
* Add a 'waiting' column to pg_stat_activity to carry the same informationTom Lane2006-08-191-1/+1
| | | | | | | that ps_status provides by appending 'waiting' to the PS display. This completes the project of making it feasible to turn off process title updates and instead rely on pg_stat_activity. Per my suggestion a few weeks ago.
* Support INSERT/UPDATE/DELETE RETURNING in plpgsql, with rowcount checkingTom Lane2006-08-142-0/+256
| | | | | | as per yesterday's proposal. Also make things a tad more orthogonal by adding the recent STRICT addition to EXECUTE INTO. Jonah Harris and Tom Lane
* If test postmaster fails to start within 60 seconds, try to kill -9 itTom Lane2006-08-131-3/+19
| | | | | so that it won't interfere with later trials. Per recent buildfarm experience. Anyone know how to do this on Windows?
* Extend 'guc' regression test to check manipulations of datestyle asTom Lane2006-08-132-12/+347
| | | | | | | | well as vacuum_cost_delay. Since datestyle is a string variable, this exercises memory allocation issues that might not appear when modifying an integer GUC variable. Also, we can observe the side effects of changing datestyle to check that assign hooks are called at the right times.
* Original coding of 'returning' regression test inadvertently chose aTom Lane2006-08-132-10/+10
| | | | | | nonunique join value, leading to plan-choice-dependent results ... and it seems some platforms will choose a different plan. Tweak the test so that it has well-defined results. Per report from Olivier Prenant.
* Add INSERT/UPDATE/DELETE RETURNING, with basic docs and regression tests.Tom Lane2006-08-124-3/+286
| | | | | | | | plpgsql support to come later. Along the way, convert execMain's SELECT INTO support into a DestReceiver, in order to eliminate some ugly special cases. Jonah Harris and Tom Lane
* Tweak sanity_check regression test to display more tables (viz, thoseTom Lane2006-08-062-72/+142
| | | | | | | | without indexes) but not to display temp tables. It's a bit hard to credit that sanity_check could get through a database-wide VACUUM while the preceding create_index test is still trying to clean up its temp tables ... but I see no other explanation for the current failure report from buildfarm member sponge.
* Add some basic tests of GUC behavior.Tom Lane2006-08-044-4/+222
| | | | Joachim Wieland
* Remove use of a regex character class in resultmap (for freebsd versionTom Lane2006-08-031-1/+1
| | | | | | | | check). This isn't supported by pg_regress since the recent rewrite into C. While we could add char classes to pg_regress.c's code, it's not really needed at the moment: thanks to Andrew's patch to make pg_regress always accept the 'standard' comparison file, we can just drop the version check.
* A few regression tests for VALUES, from Gavin Sherry.Tom Lane2006-08-036-0/+136
|
* Remove extra argument to printf().Bruce Momjian2006-08-011-2/+2
|
* have pg_regress fall back on testing with the canonical results file if anAndrew Dunstan2006-08-011-1/+31
| | | | alternative test is specified but none succeeds.
* Fix WIN32 wait() return value macros to be accurate, particularlyBruce Momjian2006-07-301-22/+21
| | | | | | | | | because they are used for testing the return value from system(). (WIN32 doesn't overlay the return code with other failure conditions like Unix does, so they are just simple macros.) Fix regression checks to properly handle diff failures on Win32 using the new macros.
* SQL2003-standard statistical aggregates, by Sergey Koposov. I've added onlyTom Lane2006-07-284-13/+77
| | | | | | | the float8 versions of the aggregates, which is all that the standard requires. Sergey's original patch also provided versions using numeric arithmetic, but given the size and slowness of the code, I doubt we ought to include those in core.
* Aggregate functions now support multiple input arguments. I also tookTom Lane2006-07-278-73/+169
| | | | | | | | the opportunity to treat COUNT(*) as a zero-argument aggregate instead of the old hack that equated it to COUNT(1); this is materially cleaner (no more weird ANYOID cases) and ought to be at least a tiny bit faster. Original patch by Sergey Koposov; review, documentation, simple regression tests, pg_dump and psql support by moi.
* Original coding of pg_regress.c made the results and log directoriesTom Lane2006-07-271-2/+2
| | | | | with restrictive permissions, which was not the behavior of the shell script and doesn't seem very desirable. Use the umask setting instead.
* Allow units to be specified with configuration settings.Peter Eisentraut2006-07-271-1/+1
|
* Remove hard-wired lists of timezone abbreviations in favor of providingTom Lane2006-07-258-16/+6
| | | | | | | | | configuration files that can be altered by a DBA. The australian_timezones GUC setting disappears, replaced by a timezone_abbreviations setting (set this to 'Australia' to get the effect of australian_timezones). The list of zone names defined by default has undergone a bit of cleanup, too. Documentation still needs some work --- in particular, should we fix Table B-4, or just get rid of it? Joachim Wieland, with some editorializing by moi.
* Use correct ifdef test for cygwin, namely __CYGWIN__ (note underscores).Andrew Dunstan2006-07-251-3/+3
|
* Remove dubious and redundant (we think) setting of libdir in PATH for non ↵Andrew Dunstan2006-07-241-10/+1
| | | | temp-install case.
* Add libdir to PATH for Cygwin as well as WIN32 - should fix buildfarm eel.Andrew Dunstan2006-07-221-3/+3
|
* Ah, I finally realize why Magnus wanted to add a --bindir option toTom Lane2006-07-212-16/+38
| | | | | | | | | pg_regress: there's no other way to cope with testing a relocated installation. Seems better to call it --psqldir though, since the only thing we need to find in that case is psql. It'd be better if we could use find_other_exec, but that's not happening unless we are willing to install pg_regress alongside psql, which seems unlikely to happen.
* As a stopgap to get the Windows buildfarm members running again, hot-wireTom Lane2006-07-201-31/+40
| | | | | | the check on diff's exit status to check for literally 0 or 1. Someone should look into why WIFEXITED/WEXITSTATUS don't work for this, but I've spent more than enough time on it already.
* Print out diff status code when we think there's a hard failure.Tom Lane2006-07-201-4/+9
| | | | May help in debugging behavior on Windows.
* Suppress unused-variable compiler warning, per Andrew Dunstan.Tom Lane2006-07-201-1/+3
|
* Fix pg_regress.c to report tests in a parallel group when they finish,Tom Lane2006-07-201-27/+48
| | | | | | not when they're started. This mimics a subtle point of the behavior of the old shell script, and gives better feedback when watching the tests.
* Make pg_regress.c get paths from pg_config_paths.h, instead of -DTom Lane2006-07-202-12/+15
| | | | | switches passed from the Makefile. This looks like it will fix problem with virtual vs real paths under msys.
* Adjust spawn_process() to avoid unnecessary overhead processes: we canTom Lane2006-07-192-18/+24
| | | | | | just exec instead of creating a subprocess. This reduces process usage from four processes per parallel test to two. I have no idea whether a comparable optimization is possible or useful in the Windows port.
* Adjust pg_regress to print out the exact string given to system() whenTom Lane2006-07-191-7/+6
| | | | | 'make install' or 'initdb' fails. Also minor simplification of fgets() usage --- fgets guarantees a trailing null anyway.
* kill() is declared in <signal.h> per Single Unix Spec.Tom Lane2006-07-191-1/+2
|
* Tweak command quoting for Windows (I'd forgotten about SYSTEMQUOTE).Tom Lane2006-07-191-12/+12
|
* Remove unnecessary inclusion of libpq into pg_regress --- overlyTom Lane2006-07-191-2/+2
| | | | enthusiastic copy and paste ...
* Rewrite pg_regress as a C program instead of a shell script.Tom Lane2006-07-194-801/+1626
| | | | | | | This allows it to be used on Windows without installing mingw (though you do still need 'diff'), and opens the door to future improvements such as message localization. Magnus Hagander and Tom Lane.
View Lorry Controller Status