aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Patch possible portability problem: a few places had // style comments,Tom Lane2000-03-17
| | | | which is not ANSI C, even though some compilers will take it...
* Typo correction (// -> /)Tom Lane2000-03-17
|
* Add safety check on expression nesting depth. Default value is set byTom Lane2000-03-17
| | | | a config.h #define, and the runtime value can be controlled via SET.
* Fix a bunch of minor portability problems and maybe-bugs revealed byTom Lane2000-03-17
| | | | | | running gcc and HP's cc with warnings cranked way up. Signed vs unsigned comparisons, routines declared static and then defined not-static, that kind of thing. Tedious, but perhaps useful...
* Update config.guess and config.sub to latest versions available fromTom Lane2000-03-16
| | | | the GNU Autoconf CVS server.
* Tweak horology regress test to ensure platform-independent ordering ofTom Lane2000-03-16
| | | | results in conversions tests. Update horology-no-DST-before-1970.out.
* Since it has been confirmed working on the bugs list, please apply theBruce Momjian2000-03-16
| | | | | | attached patch. Andreas Kardos
* libpq++ Makefile uses -DDEBUG to turn on debugging trace toBruce Momjian2000-03-16
| | | | | | | | | | | | /tmp/trace.out. However, elog.h uses DEBUG as a log-level flag. As a result, tracing is turned on even if the libpq++.so is built with DEBUG commented out in the Makefile. This patch changes libpq++ to use DEBUGFILE instead (which is not defined anywhere else). Oliver Elphick
* Support full POSIX-style time zone: EST+3, PST-3, etc.Thomas G. Lockhart2000-03-16
| | | | | | We probably support a superset of the spec, but I don't have the spec to confirm this. Update regression tests to include tests for this format.
* Support full POSIX-style time zone: EST+3, PST-3, etc.Thomas G. Lockhart2000-03-16
| | | | | | | | We probably support a superset of the spec, but I don't have the spec to confirm this. Update regression tests to include tests for this format. Update geometry.out with results from Linux RH 5.2 system (for last decimal place).
* Support full POSIX-style time zone: EST+3, PST-3, etc.Thomas G. Lockhart2000-03-16
| | | | | | | We probably support a superset of the spec, but I don't have the spec to confirm this. Update regression tests to include tests for this format. Fix single-space typo in printed message in regress.sh.
* Fixes for char_length() change.Tatsuo Ishii2000-03-16
|
* Fixes for char_length() changes.Tatsuo Ishii2000-03-16
|
* Turns out that Mazurkiewicz's gripe about 'function inheritance' isTom Lane2000-03-16
| | | | | | actually a type-coercion problem. If you have a function defined on class A, and class B inherits from A, then the function ought to work on class B as well --- but coerce_type didn't know that. Now it does.
* Fix for char_length() changesTatsuo Ishii2000-03-16
|
* Fix some (more) problems with subselects in rules. Rewriter failed toTom Lane2000-03-16
| | | | | | | mark query as having subselects if a subselect was added from a rule WHERE condition (as opposed to a rule action). Also, fix adjustment of varlevelsup so that it actually has some prospect of working when inserting an expression containing a subselect into a subquery.
* Hi,Bruce Momjian2000-03-16
| | | | | | | | | | small changes in formatting.c code (better memory usage ...etc.) and better to_char's cache (will fastly for more to_char()s in one query). (It is probably end of to_char() development in 7.0 cycle.) Karel
* Update comment obsoleted by Thomas's latest fixes.Tom Lane2000-03-15
|
* Tweak GROUP BY so that it will still accept result-column names, but onlyTom Lane2000-03-15
| | | | | | | | | | after trying to resolve the item as an input-column name. This allows us to be compliant with the SQL92 spec for queries that fall within the spec, while still accepting the same out-of-spec queries as 6.5 did. You'll only lose if there is an output column name that is the same as an input column name, but doesn't refer to the same value. 7.0 will interpret such a GROUP BY spec differently than 6.5 did. No way around that, because 6.5 was clearly not spec compliant.
* *** empty log message ***Michael Meskes2000-03-15
|
* Fix busted TRANSLATE() code --- it coredumped due to pfree()'ing theTom Lane2000-03-15
| | | | wrong pointer.
* Remove another incorrect UserAbortTransactionBlock() call.Tom Lane2000-03-15
|
* Remove gratuitous and incorrect begin/commit transaction calls inTom Lane2000-03-15
| | | | | | | | CREATE DB/DROP DB. If you didn't think they were wrong, try what happens when you compile with -DCLOBBER_FREED_MEMORY --- database name displayed in error messages is trashed, because transaction abort freed it. Also, remove trailing periods in error messages, per our prevailing style.
* Fix a couple of missed changes in expected results.Tom Lane2000-03-15
|
* Add 'datetime' -> 'timestamp' conversion to xlateSqlFunc() to easeTom Lane2000-03-15
| | | | | the pain of updating apps to 7.0. Should we also translate some of the 'datetime_foo' functions that exist in 6.* ?
* Repair unintentional damage to MULTIBYTE code.Tom Lane2000-03-14
|
* Cache fmgr lookup data for index's getnext() function in IndexScanDesc,Tom Lane2000-03-14
| | | | | so that the fmgr lookup only has to happen once per index scan and not once per tuple. Seems to save 5% or so of CPU time for an indexscan.
* Implement column aliases on views "CREATE VIEW name (collist)".Thomas G. Lockhart2000-03-14
| | | | | | | | | | | | | | | | | | Implement TIME WITH TIME ZONE type (timetz internal type). Remap length() for character strings to CHAR_LENGTH() for SQL92 and to remove the ambiguity with geometric length() functions. Keep length() for character strings for backward compatibility. Shrink stored views by removing internal column name list from visible rte. Implement min(), max() for time and timetz data types. Implement conversion of TIME to INTERVAL. Implement abs(), mod(), fac() for the int8 data type. Rename some math functions to generic names: round(), sqrt(), cbrt(), pow(), etc. Rename NUMERIC power() function to pow(). Fix int2 factorial to calculate result in int4. Enhance the Oracle compatibility function translate() to work with string arguments (from Edwin Ramirez). Modify pg_proc system table to remove OID holes.
* Marginal performance improvement in LockBuffer --- calculate addressTom Lane2000-03-14
| | | | | | of BufferLocks[] entry just once. Seems to save 10% or so of the routine's runtime, which'd not be worth worrying about if it weren't such a hotspot.
* > I have improved the System V semaphore emulation of the QNX4 port.Bruce Momjian2000-03-14
| | | | | | | | | | Please > apply the attached patch to > > backend/port/qnx4 > > Andreas Kardos >
* > To make PostgreSQL compilable on Digital Unix I had to modify theBruce Momjian2000-03-14
| | | | | | | | alpha_cc > template file. Patch attached. > > Andreas Kardos >
* > Here is an extension of the regression test suite for Digital UnixBruce Momjian2000-03-14
| | | | | | (Alpha). > > Andreas Kardos
* > Here is an extension of the regression test suite for Digital UnixBruce Momjian2000-03-14
| | | | | (Alpha). >
* > The snprintf stuff in interfaces/ecpg/preproc/Makefile.in is broken.Bruce Momjian2000-03-14
| | | | | | | | | Please > apply the attached patch. > > Andreas Kardos > >
* Detect postmaster being ready by calling psql -l rathern thanTatsuo Ishii2000-03-14
| | | | | checking postmaster.pid. It's not enough to check the existence of postmaster.pid since DB recovery might be running.
* Fix some bogosities in the code that deals with estimating the fractionTom Lane2000-03-14
| | | | | of tuples we are going to retrieve from a sub-SELECT. Must have been half asleep when I did this code the first time :-(
* Fixed deficiency where an unterminated (no semicolon) command at end ofPeter Eisentraut2000-03-13
| | | | psql script would be dropped silently.
* Extend numeric_round and numeric_trunc to accept negative scale inputsTom Lane2000-03-13
| | | | | | (ie, allow rounding to occur at a digit position left of the decimal point). Apparently this is how Oracle handles it, and there are precedents in other programming languages as well.
* Remove unnecessary limitations on lengths of bpchar and varchar constants.Tom Lane2000-03-13
| | | | | | Since we detect oversize tuples elsewhere, I see no reason not to allow string constants that are 'too long' --- after all, they might never get stored in a tuple at all.
* Performance improvement for lexing long strings: increase flex'sTom Lane2000-03-13
| | | | | | YY_READ_BUF_SIZE, which turns out to have nothing to do with buffer size. It's just a totally arbitrary upper limit on how much data myinput() is asked for at one time.
* Somehow, the variant NATIONAL CHAR [ VARYING ] was missing from theTom Lane2000-03-12
| | | | set of SQL-standard type names that we accept.
* Fix performance bug in constant-expression simplifier. After findingTom Lane2000-03-12
| | | | | | | | | that the inputs to a given operator can be recursively simplified to constants, it was evaluating the operator using the op's *original* (unsimplified) arg list, so that any subexpressions had to be evaluated again. A constant subexpression at depth N got evaluated N times. Probably not very important in practical situations, but it made us look real slow in MySQL's 'crashme' test...
* Fix performance problem in fireRIRonSubselect: with nested subqueries,Tom Lane2000-03-12
| | | | | fireRIRonSubselect was invoked twice at each subselect, leading to an exponential amount of wasted effort.
* Clean up grammar's handling of NULL in expressions: a_expr_or_null isTom Lane2000-03-12
| | | | | | | gone, replaced by plain a_expr. The few places where we needed to distinguish NULL from a_expr are now handled by tests inside the actions rather than by separate productions. This allows us to accept queries like 'SELECT 1 + NULL' without requiring parentheses around the NULL.
* Further tweaking of logic that decides when to materialize an uncorrelatedTom Lane2000-03-11
| | | | | | | subplan: do it if subplan has subplans itself, and always do it if the subplan is an indexscan. (I originally set it to materialize an indexscan only if the indexqual is fairly selective, but I dunno what I was thinking ... an unselective indexscan is still expensive ...)
* Make TypeCategory think that NAME is a member of typeTom Lane2000-03-11
| | | | | category STRING. Also, if UNKNOWNOID is passed in, return UNKNOWN_TYPE not USER_TYPE.
* Further fixes for bogus list-slinging, scribbling on input, etc in typeTom Lane2000-03-11
| | | | | | | | | coercion code. I'm beginning to wonder why we have separate candidate selection routines for functions, operators, and aggregates --- shouldn't this code all be unified? But meanwhile, SELECT 'a' LIKE 'a'; finally works; the code for dealing with unknown input types for operators was pretty busted.
* Karel Zakr's revised patch to fix psql prompt for local host connections.Peter Eisentraut2000-03-11
|
* exec_simple_check_plan() must not allow a plan having initPlans orTom Lane2000-03-11
| | | | | subPlans to be considered 'simple'. This fixes reported problem with 'return exists (select 1 from foo);' in plpgsql function.
* Finish cleaning up backend's handling of /* ... */ and -- comments,Tom Lane2000-03-11
| | | | | | | per pghackers discussion around 20-Feb. Also add specific error messages for unterminated comments and unterminated quoted strings. These things are nonissues for input coming from psql, but they do matter for input coming from other front ends.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-04 18:31:47 +0000