aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Synced preproc.y and keywords.c.Michael Meskes2002-04-22
|
* 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.
* Update horology-no-DST-before-1970.out (tested on HPUX), plus an ↵Tom Lane2002-04-21
| | | | | | extrapolated horology-solaris-1947.out (needs verification).
* Provide new option "--enable-integer-datetimes". Defaults to disabled forThomas G. Lockhart2002-04-21
| | | | now, but we may want otherwise on systems which support it.
* 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.
* Include stdio.h and stdlib.h for completeness.Thomas G. Lockhart2002-04-21
|
* 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.
* Augment the date/time examples in the User's Guide to reflect the newerThomas G. Lockhart2002-04-21
| | | | | | | | | capabilities of specifying time zones as intervals per SQL9x. Put refentrytitle contents on the same line as the tag. Otherwise, leading whitespace is propagated into the product, which (at least) messes up the ToC layout. Remove (some) docinfo tags containing dates. Best to omit if the dates are not accurate; maybe use CVS dates instead or leave them out.
* Minor wording change for readability.Thomas G. Lockhart2002-04-21
|
* Make pg_dump independent of FUNC_MAX_ARGS.Peter Eisentraut2002-04-21
|
* 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().
* Add missing include.Peter Eisentraut2002-04-20
|
* 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.
* Rule names are now unique per-relation, rather than unique globally.Tom Lane2002-04-18
| | | | | | | | DROP RULE and COMMENT ON RULE syntax adds an 'ON tablename' clause, similar to TRIGGER syntaxes. To allow loading of existing pg_dump files containing COMMENT ON RULE, the COMMENT code will still accept the old syntax --- but only if the target rulename is unique across the whole database.
* Suggest another possible solution for funcs using temp tables:Bruce Momjian2002-04-18
| | | | | < without using PL/PgSQL EXECUTE, needs cached plan invalidation > without using PL/PgSQL EXECUTE, needs cache prevention/invalidation
* More neutral:Bruce Momjian2002-04-18
| | | | > o Abort all, some or, no SET changes made in an aborted transaction
* Update:Bruce Momjian2002-04-18
| | | | > o Abort all or commit all SET changes made in an aborted transaction
* Correct documention of lo_unlink return value as int, not Oid.Bruce Momjian2002-04-18
|
* Update:Bruce Momjian2002-04-18
| | | | | > o Allow Java server-side programming, http://pljava.sourceforge.net > [java]
* Ant 1.4.1 now requires for jdbc. Mention in HISTORY release notes.Bruce Momjian2002-04-18
|
* Add how to get database/user listing information.Bruce Momjian2002-04-18
|
* Add user:Bruce Momjian2002-04-18
| | | | > * Rod is Rod Taylor <rbt@zort.ca>
* Add to DROP COLUMN.Bruce Momjian2002-04-18
|
* Add to PREPARE archive.Bruce Momjian2002-04-18
|
* Update for Neil:Bruce Momjian2002-04-18
| | | | | > * Cache most recent query plan(s) (Neil) [prepare] > * Neil is Neil Conway <nconway@klamath.dyndns.org>
* Update for Oleg:Bruce Momjian2002-04-18
| | | | > using a sequential scan for highest/lowest values (Oleg)
* Add:Bruce Momjian2002-04-18
| | | | Add to DROP COLUMN description.
* Update:Bruce Momjian2002-04-18
| | | | > o Abort SET changes made in aborted transactions (?)
* Back out python change, needs delay.Bruce Momjian2002-04-18
|
* Change docs to do 20! rather than larger.Bruce Momjian2002-04-18
|
* Updated:Bruce Momjian2002-04-18
| | | | | > * Add BETWEEN ASYMMETRIC/SYMMETRIC (Christopher) > * Christopher is Christopher Kings-Lynne <chriskl@familyhealth.com.au>
* Add:Bruce Momjian2002-04-18
| | | | > * Add BSD-licensed qsort() for Solaris
* Add:Bruce Momjian2002-04-18
| | | | > o Allow SHOW to output as a query result, like EXPLAIN
* Add mention of -DLINUX_PROFILE to profile mention.Bruce Momjian2002-04-18
|
* Add:Bruce Momjian2002-04-18
| | | | > * Try flex flags -Cf and -CF to see if performance improves
* Add:Bruce Momjian2002-04-17
| | | | > * Add utility to compute accurate random_page_cost value
* Opclasses live in namespaces. I also took the opportunity to createTom Lane2002-04-17
| | | | | | | an 'opclass owner' column in pg_opclass. Nothing is done with it at present, but since there are plans to invent a CREATE OPERATOR CLASS command soon, we'll probably want DROP OPERATOR CLASS too, which suggests that a notion of ownership would be a good idea.
* Add:Bruce Momjian2002-04-17
| | | | > * Allow easy display of usernames in a group
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 16:52:51 +0000