summaryrefslogtreecommitdiff
path: root/src/test/regress/output
Commit message (Collapse)AuthorAgeFilesLines
* GIN: Generalized Inverted iNdex.Teodor Sigaev2006-05-022-1/+5
| | | | text[], int4[], Tsearch2 support for GIN.
* Improve parser so that we can show an error cursor position for errorsTom Lane2006-03-142-3/+3
| | | | | | | | | | | during parse analysis, not only errors detected in the flex/bison stages. This is per my earlier proposal. This commit includes all the basic infrastructure, but locations are only tracked and reported for errors involving column references, function calls, and operators. More could be done later but this seems like a good set to start with. I've also moved the ReportSyntaxErrorPosition logic out of psql and into libpq, which should make it available to more people --- even within psql this is an improvement because warnings weren't handled by ReportSyntaxErrorPosition.
* Clean up CREATE FUNCTION syntax usage in contrib and elsewhere, inPeter Eisentraut2006-02-272-28/+28
| | | | | particular get rid of single quotes around language names and old WITH () construct.
* Add TABLESPACE and ON COMMIT clauses to CREATE TABLE AS. ON COMMIT isNeil Conway2006-02-191-0/+21
| | | | | required by the SQL standard, and TABLESPACE is useful functionality. Patch from Kris Jurka, minor editorialization by Neil Conway.
* Create a standard function pg_sleep() to sleep for a specified amount of time.Tom Lane2006-01-111-4/+0
| | | | | Replace the former ad-hoc implementation used in the regression tests. Joachim Wieland
* Change nextval and other sequence functions to specify their sequenceTom Lane2005-10-021-2/+1
| | | | | | | | | | | | | | | argument as a 'regclass' value instead of a text string. The frontend conversion of text string to pg_class OID is now encapsulated as an implicitly-invocable coercion from text to regclass. This provides backwards compatibility to the old behavior when the sequence argument is explicitly typed as 'text'. When the argument is just an unadorned literal string, it will be taken as 'regclass', which means that the stored representation will be an OID. This solves longstanding problems with renaming sequences that are referenced in default expressions, as well as new-in-8.1 problems with renaming such sequences' schemas or moving them to another schema. All per recent discussion. Along the way, fix some rather serious problems in dbmirror's support for mirroring sequence operations (int4 vs int8 confusion for instance).
* In the stats test, delay for the stats collector to catch up using aTom Lane2005-07-231-5/+9
| | | | | function that actually sleeps, instead of busy-waiting. Perhaps this will resolve some of the intermittent stats failures we keep seeing.
* Add E'' syntax so eventually normal strings can treat backslashesBruce Momjian2005-06-261-6/+6
| | | | | | | | | | | | literally. Add GUC variables: "escape_string_warning" - warn about backslashes in non-E strings "escape_string_syntax" - supports E'' syntax? "standard_compliant_strings" - treats backslashes literally in '' Update code to use E'' when escapes are used.
* Regression tests for the COPY CSV header feature. From Andrew Dunstan.Neil Conway2005-05-101-0/+10
|
* Fix minor breakage to regression tests induced in previous commit -- I hadNeil Conway2005-04-071-0/+2
| | | | updated the expected/ output, not the output/ output. Apologies.
* First phase of OUT-parameters project. We can now define and use SQLTom Lane2005-03-311-1/+1
| | | | | functions with OUT parameters. The various PLs still need work, as does pg_dump. Rudimentary docs and regression tests included.
* Add CVS \r\n regression tests.Bruce Momjian2005-03-161-0/+27
| | | | Andrew Dunstan
* Create 'default_tablespace' GUC variable that supplies a TABLESPACETom Lane2004-11-051-12/+4
| | | | | | | | | | clause implicitly whenever one is not given explicitly. Remove concept of a schema having an associated tablespace, and simplify the rules for selecting a default tablespace for a table or index. It's now just (a) explicit TABLESPACE clause; (b) default_tablespace if that's not an empty string; (c) database's default. This will allow pg_dump to use SET commands instead of tablespace clauses to determine object locations (but I didn't actually make it do so). All per recent discussions.
* Tablespaces. Alternate database locations are dead, long live tablespaces.Tom Lane2004-06-181-0/+45
| | | | | | | | | There are various things left to do: contrib dbsize and oid2name modules need work, and so does the documentation. Also someone should think about COMMENT ON TABLESPACE and maybe RENAME TABLESPACE. Also initlocation is dead, it just doesn't know it yet. Gavin Sherry and Tom Lane.
* Clean up generation of default names for constraints, indexes, and serialTom Lane2004-06-101-4/+4
| | | | | | | | sequences, as per recent discussion. All these names are now of the form table_column_type, with digits added if needed to make them unique. Default constraint names are chosen to be unique across their whole schema, not just within the parent object, so as to be more SQL-spec-compatible and make the information schema views more useful.
* Promote row expressions to full-fledged citizens of the expression syntax,Tom Lane2004-05-102-2/+41
| | | | | | | | | | rather than allowing them only in a few special cases as before. In particular you can now pass a ROW() construct to a function that accepts a rowtype parameter. Internal generation of RowExprs fixes a number of corner cases that used to not work very well, such as referencing the whole-row result of a JOIN or subquery. This represents a further step in the work I started a month or so back to make rowtype values into first-class citizens.
* Replace TupleTableSlot convention for whole-row variables and functionTom Lane2004-04-011-1/+17
| | | | | | | | results with tuples as ordinary varlena Datums. This commit does not in itself do much for us, except eliminate the horrid memory leak associated with evaluation of whole-row variables. However, it lays the groundwork for allowing composite types as table columns, and perhaps some other useful features as well. Per my proposal of a few days ago.
* Revise syntax-error reporting behavior to give pleasant results forTom Lane2004-03-211-2/+3
| | | | | errors in internally-generated queries, such as those submitted by plpgsql functions. Per recent discussions with Fabien Coelho.
* Teach psql to show the location of syntax errors visually, per recentTom Lane2004-03-141-0/+4
| | | | | | discussions. Patch by Fabien Coelho and Tom Lane. Still needs to be taught about multi-screen-column kanji characters; Tatsuo has promised to provide the needed infrastructure for that.
* Arrange to emit a CONTEXT: SQL function "foo" entry in an errorTom Lane2004-03-141-0/+4
| | | | | | message that is reporting a prechecking error in a SQL function. This is to cue client-side code that the syntax error position, if any, is with respect to the function body and not the outer command.
* Revise int2/int4/int8/float4/float8 input routines to allow forNeil Conway2004-03-111-1/+2
| | | | | | | | | | any amount of leading or trailing whitespace (where "whitespace" is defined by isspace()). This is for SQL conformance, as well as consistency with other numeric types (e.g. oid, numeric). Also refactor pg_atoi() to avoid looking at errno where not necessary, and add a bunch of regression tests for the input to these types.
* Improve context display for failures during COPY IN, as recentlyTom Lane2003-09-291-1/+1
| | | | discussed on pghackers.
* Forget to update the real source of the regression test results afterPeter Eisentraut2003-09-251-25/+25
| | | | message editing.
* A visit from the message-style police ...Tom Lane2003-07-281-2/+2
|
* Error message editing in backend/access.Tom Lane2003-07-211-3/+3
|
* Error message editing in backend/executor.Tom Lane2003-07-211-22/+22
|
* Another round of error message editing, covering backend/commands/.Tom Lane2003-07-201-1/+1
|
* Another round of error message editing, covering backend/parser/.Tom Lane2003-07-192-6/+6
|
* First bits of work on error message editing.Tom Lane2003-07-181-10/+14
|
* Includes:Bruce Momjian2003-06-251-1/+4
| | | | | | | | | | | | | | | | - 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>
* Adopt latest bison's spelling of 'syntax error' rather than 'parse error'Tom Lane2003-05-292-3/+3
| | | | | for grammar-detected problems. Revert Makefile hack that kept it looking like the pre-bison-1.875 output.
* Infrastructure for upgraded error reporting mechanism. elog.c isTom Lane2003-04-241-1/+2
| | | | | | | rewritten and the protocol is changed, but most elog calls are still elog calls. Also, we need to contemplate mechanisms for controlling all this functionality --- eg, how much stuff should appear in the postmaster log? And what API should libpq expose for it?
* Update for new serial functionality.Bruce Momjian2003-03-201-3/+1
|
* Initial version of the SQL information schemaPeter Eisentraut2002-12-141-2/+3
|
* Fix regression test breakage from triggers patch.Tom Lane2002-11-231-1/+3
|
* Finish implementation of hashed aggregation. Add enable_hashagg GUCTom Lane2002-11-211-1/+1
| | | | | | parameter to allow it to be forced off for comparison purposes. Add ORDER BY clauses to a bunch of regression test queries that will otherwise produce randomly-ordered output in the new regime.
* Reduce messages associated with shell-type function arguments/resultsTom Lane2002-11-011-4/+4
| | | | from WARNING to NOTICE, since they are expected messages in common cases.
* Fix ALTER TABLE ... ADD COLUMN for inheritance cases.Bruce Momjian2002-10-211-0/+1
| | | | Alvaro Herrera
* Add a bunch of pseudo-types to replace the behavior formerly associatedTom Lane2002-08-221-8/+19
| | | | | | with OPAQUE, as per recent pghackers discussion. I still want to do some more work on the 'cstring' pseudo-type, but I'm going to commit the bulk of the changes now before the tree starts shifting under me ...
* More changes to match new error format.Bruce Momjian2002-08-182-3/+3
|
* Make cluster regress test functional.Tom Lane2002-08-111-232/+0
|
* Major improvement in CLUSTER which preserves table characteristics usingBruce Momjian2002-08-101-0/+232
| | | | | | | | | | | | relfilenode. I sent the CLUSTER patch a few days ago and I think it was missed. I append it again, this time including the regression test files. For the committer, please note that you have to cvs add the files as they don't exist. Maybe add to the parallel and serial schedules also, but I don't know such stuff. Alvaro Herrera (<alvherre[a]atentus.com>)
* Change messages like this:Bruce Momjian2002-08-041-20/+20
| | | | | | | | | | | | | | | | ERROR: ExecInsert: rejected due to CHECK constraint insert_con To be like this: ERROR: ExecInsert: rejected due to CHECK constraint "insert_con" on "insert_tbl" Updated regression tests to match. I got sick of seeing 'rejected due to CHECK constraint "$1" in my log and not being able to find the bug in our website code... Christopher Kings-Lynne
* Second phase of committing Rod Taylor's pg_depend/pg_constraint patch.Tom Lane2002-07-121-2/+2
| | | | | | | | | | | | pg_relcheck is gone; CHECK, UNIQUE, PRIMARY KEY, and FOREIGN KEY constraints all have real live entries in pg_constraint. pg_depend exists, and RESTRICT/CASCADE options work on most kinds of DROP; however, pg_depend is not yet very well populated with dependencies. (Most of the ones that are present at this point just replace formerly hardwired associations, such as the implicit drop of a relation's pg_type entry when the relation is dropped.) Need to add more logic to create dependency entries, improve pg_dump to dump constraints in place of indexes and triggers, and add some regression tests.
* Change error messages ExecAppend->ExecInsert and ExecReplace->ExecUpdateBruce Momjian2002-07-111-21/+21
| | | | as discussed on hackers.
* Back out cleanup patch. Got old version and needs work.Bruce Momjian2002-06-251-21/+21
| | | | Neil Conway
* The attached patch fixes some spelling mistakes, makes theBruce Momjian2002-06-251-21/+21
| | | | | | | | | | | | | comments on one of the optimizer functions a lot more clear, adds a summary of the recent KSQO discussion to the comments in the code, adds regression tests for the bug with sequence state Tom fixed recently and another reg. test, and removes some PostQuel legacy stuff: ExecAppend -> ExecInsert, ExecRetrieve -> ExecSelect, etc. This was changed because the elog() messages from this routine are user-visible, so we should be using the SQL terms. Neil Conway
* Add optional "validator" function to languages that can validate thePeter Eisentraut2002-05-221-0/+25
| | | | | | | | | | | | function body (and other properties) as a function in the language is created. This generalizes ad hoc code that already existed for the built-in languages. The validation now happens after the pg_proc tuple of the new function is created, so it is possible to define recursive SQL functions. Add some regression test cases that cover bogus function definition attempts.
* Further cleanups for relations in schemas: teach nextval and otherTom Lane2002-03-301-1/+0
| | | | | | sequence functions how to cope with qualified names. Same code is also used for int4notin, currtid_byrelname, pgstattuple. Also, move TOAST tables into special pg_toast namespace.
* pg_type has a typnamespace column; system now supports creating typesTom Lane2002-03-291-1/+1
| | | | | | in different namespaces. Also, cleanup work on relation namespace support: drop, alter, rename commands work for tables in non-default namespaces.
View Lorry Controller Status