aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* Retire xlateSqlType/xlateSqlFunc; all type name translations are nowTom Lane2002-05-03
| | | | | | | | handled as special productions. This is needed to keep us honest about user-schema type names that happen to coincide with system type names. Per pghackers discussion 24-Apr. To avoid bloating the keyword list too much, I removed the translations for datetime, timespan, and lztext, all of which were slated for destruction several versions back anyway.
* Fix backslash-n typo, per Joe Conway.Tom Lane2002-05-02
|
* Tweak scanner/grammar interface so that the keyword-as-identifier rulesTom Lane2002-05-02
| | | | | | in gram.y can make use of the keywords.c string table, instead of having their own copies of the keyword strings. This saves a few kilobytes and more importantly eliminates an opportunity for cut-and-paste errors.
* Add routines in namespace.c to determine whether objects are visibleTom Lane2002-05-01
| | | | | | in the search path. (We might want to make these available as SQL functions too, but I haven't done that yet.) Fix format_type to be schema-aware.
* Give left_oper() and right_oper() noError parameters like oper() (theTom Lane2002-05-01
| | | | binary case) already has. Needed for upcoming ruleutils change.
* Improve lexer's error reporting. You get the whole token mentioned nowTom Lane2002-05-01
| | | | | | | | | | | | in parse error messages, not just the part scanned by the last flex rule. For example, select "foo" "bar"; used to draw ERROR: parser: parse error at or near """ which was rather unhelpful. Now it gives ERROR: parser: parse error at or near ""bar"" Also, error messages concerning bitstring literals and suchlike will quote the source text at you, not the processed internal form of the literal.
* Change heap_get_latest_tid() so that a transaction canHiroshi Inoue2002-05-01
| | | | see changes made by the transaction itself.
* Clean up loose ends remaining from schema privileges discussion.Tom Lane2002-04-30
| | | | | I concluded that RENAME should require CREATE privilege on the namespace as well as ownership of the table.
* Code review for ALTER TRIGGER RENAME patch: make better use of index,Tom Lane2002-04-30
| | | | don't scribble on tuple returned by table scan.
* Enforce EXECUTE privilege for aggregate functions.Tom Lane2002-04-29
|
* Implement checking of USAGE rights on namespaces.Tom Lane2002-04-29
|
* Add cache invalidation callback hooks.Tom Lane2002-04-29
|
* Fix problem with new pg_hba.conf code where the same comparison functionBruce Momjian2002-04-28
| | | | was incorrectly used for both qsort and bsearch.
* Second try at fixing join alias variables. Instead of attaching miscellaneousTom Lane2002-04-28
| | | | | | | | lists to join RTEs, attach a list of Vars and COALESCE expressions that will replace the join's alias variables during planning. This simplifies flatten_join_alias_vars while still making it easy to fix up varno references when transforming the query tree. Add regression test cases for interactions of subqueries with outer joins.
* Make ruleutils.c use format_type for printing typenames. Minor tweaksTom Lane2002-04-28
| | | | in quoting rules and recognition of implicit type coercions.
* Minor code cleanup.Tom Lane2002-04-28
|
* Support toasting of shared system relations, and provide toast tables forTom Lane2002-04-27
| | | | | | | | | pg_database, pg_shadow, pg_group, all of which now have potentially-long fields. Along the way, get rid of SharedSystemRelationNames list: shared rels are now identified in their include/pg_catalog/*.h files by a BKI_SHARED_RELATION macro, while indexes and toast rels inherit sharedness automatically from their parent table. Fix some bugs with failure to detoast pg_group.grolist during ALTER GROUP.
* Fix write of pg_pwd file for multiple users. Broken recently by myBruce Momjian2002-04-27
| | | | pg_hba.conf changes.
* Restructure aclcheck error reporting to make permission-failureTom Lane2002-04-27
| | | | | | | messages more uniform and internationalizable: the global array aclcheck_error_strings[] is gone in favor of a subroutine aclcheck_error(). Partial implementation of namespace-related permission checks --- not all done yet.
* Move renametrig() from tablecmds.c to trigger.c --- if we're going toTom Lane2002-04-26
| | | | | | | divide backend/commands by object type, let's try to pay at least minimal attention to respecting that structure, eh? Also reorder the contents of tablecmds.c; it seems odd to me to put ALTER commands before creation/deletion commands.
* Add current_schema() and current_schemas() inquiry functions.Tom Lane2002-04-26
| | | | | Update has_table_privilege functions to cope with schema-qualified names in the same way as nextval() and others.
* Implement types regprocedure, regoper, regoperator, regclass, regtypeTom Lane2002-04-25
| | | | | | | per pghackers discussion. Add some more typsanity tests, and clean up some problems exposed thereby (broken or missing array types for some built-in types). Also, clean up loose ends from unknownin/out patch.
* Fix password code to deal with new quoting code.Bruce Momjian2002-04-25
|
* Restrict comment to the current database in order to prevent them fromBruce Momjian2002-04-24
| | | | | | | | | | | | | | | mysteriously disappearing. ie. \d+ will only ever show the comment for the current database -- which is appropriate since it can only pull comments from the current database. Won't break pgadmin functionality as it enforces this behaviour already. I didn't find any regression tests for COMMENT. Rod Taylor
* Attached is a patch for ALTER TRIGGER RENAME per the above thread. IBruce Momjian2002-04-24
| | | | | | | | left a stub for a future "ALTER RULE RENAME" but did not write that one yet. Bruce, if you want to add my name for for that I'll take it and do it later. Joe Conway
* Doc fix for INSERT ... (DEFAULT, ...)Bruce Momjian2002-04-24
| | | | | | Appears I forgot to update the docs earlier. Rod Taylor
* Reports missing values as bad.Bruce Momjian2002-04-24
| | | | | | | | | | BAD: INSERT INTO tab (col1, col2) VALUES ('val1'); GOOD: INSERT INTO tab (col1, col2) VALUES ('val1', 'val2'); Regress tests against DEFAULT and normal values as they're managed slightly different. Rod Taylor
* Here's a patch to add unknownin/unknownout support. I also poked aroundBruce Momjian2002-04-24
| | | | | | | | | | looking for places that assume UNKNOWN == TEXT. One of those was the "SET" type in pg_type.h, which was using textin/textout. This one I took care of in this patch. The other suspicious place was in string_to_dataum (which is defined in both selfuncs.c and indxpath.c). I wasn't too sure about those, so I left them be. Joe Conway
* xlog.c: If possible please add the following patch to better support NetWare.Bruce Momjian2002-04-24
| | | | Ulrich Neumann
* [ Patch comments in three pieces.]Bruce Momjian2002-04-24
| | | | | | | | | | | | | | | | | | | | Attached is a pacth against 7.2 which adds locale awareness to the character classes of the regular expression engine. ... > > I still think the xdigit class could be handled the same way the digit > > class is (by enumeration rather than using the isxdigit function). That > > saves you a cicle, and I don't think there's any loss. > > In fact, I will email you when I apply the original patch. I miss that case :-(. Here is the pached patch. ... Here is a patch which addresses Tatsuo's concerns (it does return an static struct instead of constructing it).
* Clean up INT64CONST conflicts. Make the pg_crc code use a macro calledTom Lane2002-04-23
| | | | | UINT64CONST, since unsigned was what it wanted anyway. Centralize macro definitions into c.h.
* Oops, forgot we had a macro to encapsulate test for type toastability.Tom Lane2002-04-22
|
* Fix incorrect Assert; install a more trustworthy check on whetherTom Lane2002-04-22
| | | | ALTER COLUMN SET STORAGE should be allowed.
* Convert GUC parameters back to strings if input as integers.Thomas G. Lockhart2002-04-22
| | | | | Change elog(ERROR) messages to say that a variable takes one parameter, rather than saying that it does not take multiple parameters.
* Check for multiple arguments on parameters which do not allow them.Thomas G. Lockhart2002-04-22
| | | | | The last version caught this with an assert because I wasn't sure whether we should elog(ERROR) or just loop through the parameters.
* Oops. Remove declaration for set_name_needs_quotes(), since it is now gone.Thomas G. Lockhart2002-04-21
|
* Remove the definition for set_name_needs_quotes() on the assumption thatThomas G. Lockhart2002-04-21
| | | | it is now obsolete. Need some regression test cases to prove otherwise...
* Initialize or set a couple of variables to suppress compiler warnings.Thomas G. Lockhart2002-04-21
| | | | | | These were for cases protected by elog(ERROR) exits, but may as well keep the compiler happy. Not sure why they don't show up on my gcc-2.96.x version of the compiler.
* Support alternate storage scheme of 64-bit integer for date/time types.Thomas G. Lockhart2002-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Use "--enable-integer-datetimes" in configuration to use this rather than the original float8 storage. I would recommend the integer-based storage for any platform on which it is available. We perhaps should make this the default for the production release. Change timezone(timestamptz) results to return timestamp rather than a character string. Formerly, we didn't have a way to represent timestamps with an explicit time zone other than freezing the info into a string. Now, we can reasonably omit the explicit time zone from the result and return a timestamp with values appropriate for the specified time zone. Much cleaner, and if you need the time zone in the result you can put it into a character string pretty easily anyway. Allow fractional seconds in date/time types even for dates prior to 1BC. Limit timestamp data types to 6 decimal places of precision. Just right for a micro-second storage of int8 date/time types, and reduces the number of places ad-hoc rounding was occuring for the float8-based types. Use lookup tables for precision/rounding calculations for timestamp and interval types. Formerly used pow() to calculate the desired value but with a more limited range there is no reason to not type in a lookup table. Should be *much* better performance, though formerly there were some optimizations to help minimize the number of times pow() was called. Define a HAVE_INT64_TIMESTAMP variable. Based on the configure option "--enable-integer-datetimes" and the existing internal INT64_IS_BUSTED. Add explicit date/interval operators and functions for addition and subtraction. Formerly relied on implicit type promotion from date to timestamp with time zone. Change timezone conversion functions for the timetz type from "timetz()" to "timezone()". This is consistant with other time zone coersion functions for other types. Bump the catalog version to 200204201. Fix up regression tests to reflect changes in fractional seconds representation for date/times in BC eras. All regression tests pass on my Linux box.
* Make WITHOUT TIME ZONE the default for TIMESTAMP and TIME data types.Thomas G. Lockhart2002-04-21
| | | | | | | | | | | | | | | | | This is a big change from past behavior, but the last release was designed to handle this correctly for dump/restore upgrades. Fix up handling of SET value arguments. Allow lists for most options at least at the parser level; multiple values may be rejected at the command processor of course. Allow more variations on values for SET commands, including integer and float values where formerly stringy fields were required. Check precision specification for date/time fields against the true precision range allowed by the data types. Especially useful with the new int8-based storage for these types, where precision is fixed and predictable. Stub out a basic CREATE ASSERTION per SQL9x. Does not do anything (yet) but should be augmented as appropriate. Minor fixups in braces and tabbing.
* Allow more choices for style of value in various SET commands. Formerly,Thomas G. Lockhart2002-04-21
| | | | | | | | | | | most required a stringy syntax in the parser; now integers and floats can (or should) be handled. There is at least one cheesy error message mentioning sending mail to me if there are problems; should be changed prior to release. Allow lists of values from the parser in more cases. If multiple arguments were not allowed previously, they probably are not allowed now, but at least the data structures being passed around are more consistant across more cases.
* Add fields in the control file to check for whether the backend wasThomas G. Lockhart2002-04-21
| | | | | | | | compiled for integer date/time storage and to check the length of storage for the locale fields in the same data structure. Slightly reword some of the error messages to be more accurate on possible recovery options (e.g. recompile *or* re-initdb). Bump version number on this file.
* Fix typo.Tom Lane2002-04-21
|
* Restructure AclItem representation so that we can have more than eightTom Lane2002-04-21
| | | | | | | | | different privilege bits (might as well make use of the space we were wasting on padding). EXECUTE and USAGE bits for procedures, languages now are separate privileges instead of being overlaid on SELECT. Add privileges for namespaces and databases. The GRANT and REVOKE commands work for these object types, but we don't actually enforce the privileges yet...
* Remove --enable-syslog optionTatsuo Ishii2002-04-21
|
* pq_getstring doesn't go through pq_getbyte anymore, for better performance.Peter Eisentraut2002-04-20
|
* Scanner performance improvementsPeter Eisentraut2002-04-20
| | | | | | | | Use flex flags -CF. Pass the to-be-scanned string around as StringInfo type, to avoid querying the length repeatedly. Clean up some code and remove lex-compatibility cruft. Escape backslash sequences inline. Use flex-provided yy_scan_buffer() function to set up input, rather than using myinput().
* Change naming rule for ON SELECT rules of views: they're all justTom Lane2002-04-19
| | | | _RETURN now, since there's no need to keep 'em unique anymore.
* pg_trigger's index on tgrelid is replaced by a unique index onTom Lane2002-04-19
| | | | | | | | | | (tgrelid, tgname). This provides an additional check on trigger name uniqueness per-table (which was already enforced by the code anyway). With this change, RelationBuildTriggers will read the triggers in order by tgname, since it's scanning using this index. Since a predictable trigger ordering has been requested for some time, document this behavior as a feature. Also document that rules fire in name order, since yesterday's changes to pg_rewrite indexing cause that too.
* Make PUBLIC an unreserved word (in fact, not a keyword at all),Tom Lane2002-04-18
| | | | per previous discussion.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 20:15:14 +0000