aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* Back out qnx plpgsql/Makefile change and move to src/Makefile.Bruce Momjian2001-05-24
|
* I haven't tried building postgres with the Watcom compiler for 7.1 becauseBruce Momjian2001-05-24
| | | | | | | | | | | | | | | | it does not support 64bit integers. AFAIK that's the default data type for OIDs, so I am not surprised that this does not work. Use gcc instead. BTW., 7.1 does not compile as is with gcc either, I believed the required patches made it into the 7.1.1 release but obviously I missed the deadline. Since the ports mailing list does not seem to be archived I have attached a copy of the patch (for 7.1 and 7.1.1). I've just performed a build of a Watcom compiled version and found a couple of bugs in the watcom specific part of that patch. Please use the attached version instead. Tegge, Bernd
* There are a number of changes. The main ones are:Bruce Momjian2001-05-24
| | | | | | | | | | | return oid on insert handle all primitive data types handle single quotes and newlines in Strings handle null variables deal with non public and final variables (not very well, though) Ken K
* SQL function bit_lengthPeter Eisentraut2001-05-24
|
* Unset PGLIB so it doesn't slip in from the environment.Peter Eisentraut2001-05-24
|
* Make createlang use dynamic loader enhancements (automatic path and suffix).Peter Eisentraut2001-05-23
|
* Fix ANT for *.properties files.Bruce Momjian2001-05-23
|
* Fix ANT so it only has '*.class' files, not the 'tags' file.Bruce Momjian2001-05-23
|
* Back out timezone fix. Not needed in jdbc1.Bruce Momjian2001-05-22
|
* Fix for comments at top of functions.Bruce Momjian2001-05-22
|
* I found the answer to this: the partition had filled up, and so the problemBruce Momjian2001-05-22
| | | | | | was lack of disk space. Oliver Elphick
* Make bit and bit varying types reject too long input. (They already triedPeter Eisentraut2001-05-22
| | | | | | to do that, but inconsistently.) Make bit type reject too short input, too, per SQL. Since it no longer zero pads, 'zpbit*' has been renamed to 'bit*' in the source, hence initdb.
* The Watcom preprocessor adds a space at the start of each line. ThereforeBruce Momjian2001-05-22
| | | | | | | the output of "egrep '^[0-9]' " is empty. Changing the pattern to "egrep '^[ ]*[0-9]" generates the correct file. Tegge, Bernd
* Bump major libpq++ version after API changes, Patrick WelcheBruce Momjian2001-05-22
|
* Pgindent fixes for Tom, mostly indenting problems.Bruce Momjian2001-05-22
|
* Print error on SELECT tab FROM tab:Bruce Momjian2001-05-21
| | | | You can't use relation names alone in the target list, try relation.*
* Make char(n) and varchar(n) types raise an error if the inserted string isPeter Eisentraut2001-05-21
| | | | | too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
* Enhancement of SPI to get access to portalsJan Wieck2001-05-21
| | | | | | | | | | | | | | | | | | | | | | | | | - New functions to create a portal using a prepared/saved SPI plan or lookup an existing portal by name. - Functions to fetch/move from/in portals. Results are placed in the usual SPI_processed and SPI_tuptable, so the entire set of utility functions can be used to gain attribute access. - Prepared/saved SPI plans now use their own memory context and SPI_freeplan(plan) can remove them. - Tuple result sets (SPI_tuptable) now uses it's own memory context and can be free'd by SPI_freetuptable(tuptab). Enhancement of PL/pgSQL - Uses generic named portals internally in FOR ... SELECT loops to avoid running out of memory on huge result sets. - Support for CURSOR and REFCURSOR syntax using the new SPI functionality. Cursors used internally only need no explicit transaction block. Refcursor variables can be used inside of explicit transaction block to pass cursors between main application and functions. Jan
* Modify optimizer data structures so that IndexOptInfo lists built forTom Lane2001-05-20
| | | | | | | | create_index_paths are not immediately discarded, but are available for subsequent planner work. This allows avoiding redundant syscache lookups in several places. Change interface to operator selectivity estimation procedures to allow faster and more flexible estimation. Initdb forced due to change of pg_proc entries for selectivity functions!
* Make sure fmgr_info() fills in fn_oid last, so that no partiallyPeter Eisentraut2001-05-19
| | | | initialized FmgrInfo structs linger after elog.
* Allow special '$libdir' macro to show up in object file path in CREATEPeter Eisentraut2001-05-19
| | | | | FUNCTION command. Guard against trying to load a directory. Update documentation some.
* Prevent ANT from recreating the JAR files just because theBruce Momjian2001-05-19
| | | | errors.properties files were being copied.
* Comment additions in parser.Bruce Momjian2001-05-19
|
* Move ParserFuncOrColumn function higher in the file.Bruce Momjian2001-05-19
|
* New comment. This func/column things has always confused me.Bruce Momjian2001-05-19
| | | | | | | | | | | | | | | | | | | /* * parse function * This code is confusing because the database can accept * relation.column, column.function, or relation.column.function. * In these cases, funcname is the last parameter, and fargs are * the rest. * * It can also be called as func(col) or func(col,col). * In this case, Funcname is the part before parens, and fargs * are the part in parens. * */ Node * ParseFuncOrColumn(ParseState *pstate, char *funcname, List *fargs, bool agg_star, bool agg_distinct, int precedence)
* Undo \dT change. Not worth it.Bruce Momjian2001-05-18
|
* Rename ParseFuncOrColumn() to ParseColumnOrFunc().Bruce Momjian2001-05-18
|
* Small code cleanups,formatting.Bruce Momjian2001-05-18
|
* Adding ELSIF support contributed by Klaus Reger.Jan Wieck2001-05-18
| | | | Jan
* Suppress compiler warnings about pid_t vs int.Tom Lane2001-05-18
|
* Add regression test to catch future breakage of avg(interval). ThisTom Lane2001-05-18
| | | | | aggregate seems uniquely fragile, because it's the only one with an agginitval that's at all likely to change in format.
* Correct recently-broken avg(interval) definition.Tom Lane2001-05-18
|
* Add -U and -W options to pg_dump and friends to support non-interactivePeter Eisentraut2001-05-17
| | | | | specification of username (like in psql). pg_dumpall now works with password authentication.
* Add dynamic_library_path parameter and automatic appending of sharedPeter Eisentraut2001-05-17
| | | | library extension.
* OK, now pgindent has blank lines before comment blocks, except whenBruce Momjian2001-05-17
| | | | there is a brace on the line above it.
* Prevent forced blank line before comment block in pgindent.Bruce Momjian2001-05-17
|
* Spacing cleanup.Bruce Momjian2001-05-17
|
* Small cleanup of spacing.Bruce Momjian2001-05-17
|
* Add HISTORY items for 7.1.2.Bruce Momjian2001-05-17
|
* Add missing space to sample cvs call.Bruce Momjian2001-05-17
|
* Fix pg_index statistics query to join proper relation.Bruce Momjian2001-05-17
|
* Included is a patch that fixes a bug introduced in the lastest versionBruce Momjian2001-05-17
| | | | | | | | | | | | | | (1.22) of interfaces/jdbc/org/postgresql/jdbc2/ResultSet.java. That change removed a line that set the variable s to the value of the stringbuffer. This fix changes the following if checks to check the length of the stringbuffer instead of s, since s no longer contains the string the if conditions are expecting. The bug manifests itself in getTimestamp() loosing the timezone information of timestamps selected from the database, thereby causing the time to be incorrect. Barry Lind
* Cleanup of backpatch of jdbc2 improvements to jdbc1:Bruce Momjian2001-05-17
| | | | | | | | | | | | | | | Here's what I came up with. The biggest difference api between JDK1.x and later versions is the support for collections. The problem was with the Vector class; in jdk1.x there is no method called add, so I changed the calls to addElement. Also no addAll, so I rewrote the method slightly to not require addAll. While reviewing this I notices some System.out.println statements that weren't commented out. So I commented them out in both versions. The upshot of all of this is that I have clean compile, but no idea if the code works ;( Dave Cramer
* Fix 'make clean' with jdbc and ant by using filesets.Bruce Momjian2001-05-17
|
* 1) Decrease the size of some buffers.Hiroshi Inoue2001-05-17
| | | | 2) Repair broken SQLStatistics().
* Replace poorly-coded vac_find_eq routine with call to standard bsearchTom Lane2001-05-17
| | | | | library code. Tweak progress messages to include elapsed real time, not only CPU time.
* Mark column as not used.Bruce Momjian2001-05-17
|
* Add missing paren.Bruce Momjian2001-05-16
|
* Repair race condition introduced into heap_update() in 7.1 ---Tom Lane2001-05-16
| | | | | | | | | | | | | | | PageGetFreeSpace() was being called while not holding the buffer lock, which not only could yield a garbage answer, but even if it's the right answer there might be less space available after we reacquire the buffer lock. Also repair potential deadlock introduced by my recent performance improvement in RelationGetBufferForTuple(): it was possible for two heap_updates to try to lock two buffers in opposite orders. The fix creates a global rule that buffers of a single heap relation should be locked in decreasing block number order. Currently, this only applies to heap_update; VACUUM can get away with ignoring the rule since it holds exclusive lock on the whole relation anyway. However, if we try to implement a VACUUM that can run in parallel with other transactions, VACUUM will also have to obey the lock order rule.
* Fix for HASH for index lookups in ODBC.Bruce Momjian2001-05-16
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-05 09:58:10 +0000