aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
* Attached is my patch that adds DROP CONSTRAINT support to PostgreSQL. IBruce Momjian2001-05-30
| | | | | | | | | | | | | | | | | | | | basically want your guys feedback. I have sprinkled some of my q's thru the text delimited with the @@ symbol. It seems to work perfectly. [ Removed @@ comments because patch was reviewed. ] At the moment it does CHECK constraints only, with inheritance. However, due to the problem mentioned before with the mismatching between inherited constraints it may be wise to disable the inheritance feature for a while. it is written in an extensible fashion to support future dropping of other types of constraint, and is well documented. Please send me your comments, check my use of locking, updating of indices, use of ERROR and NOTICE, etc. and I will rework the patch based on feedback until everyone is happy with it... Christopher Kings
* Add missing comma.D'Arcy J.M. Cain2001-05-30
|
* Make text <=> char conversion functions convert zero character to andTom Lane2001-05-28
| | | | | | from an empty text string. This makes them consistent with the de facto behavior of type char's I/O conversion functions, and avoids generating text values with embedded nulls, which confuse many text operators.
* Cause plpgsql's PERFORM to behave according to its documentation,Tom Lane2001-05-28
| | | | | | | | | | | | which says that PERFORM will execute any SELECT query and discard the result. The former implementation would in fact raise an error if the result contained more than one row or more than one column. Also, change plpgsql's error-logging mechanism to emit the additional messages about error location at NOTICE rather than DEBUG level. This allows them to be seen by the client without having to dig into the postmaster log file (which may be nonexistent or inaccessible by the client).
* Suppress useless memmove() when buffer already contains left-justifiedTom Lane2001-05-28
| | | | data.
* This just breaks down the indices in to three groups:Bruce Momjian2001-05-28
| | | | | | | | | | | | non-unique: stay as they were unique and primary: become listed as primary keys unique and non-primary: become listed as unique keys I also made it so that it shows the names of check constraints ie: Check: "$1" (a > 5) Christopher Kings
* Fix a message error in utf_to_localTatsuo Ishii2001-05-28
|
* Attached is a patch to fix the problem Thomas mentions below. The JDBCBruce Momjian2001-05-28
| | | | | | | driver now correctly handles timezones that are offset fractional hours from GMT (ie. -06:30). Barry Lind
* Don't use multi-line string literals.Peter Eisentraut2001-05-27
|
* When using a junkfilter, the output tuple should NOT be stored back intoTom Lane2001-05-27
| | | | | | | | the same tuple slot that the raw tuple came from, because that slot has the wrong tuple descriptor. Store it into its own slot with the correct descriptor, instead. This repairs problems with SPI functions seeing inappropriate tuple descriptors --- for example, plpgsql code failing to cope with SELECT FOR UPDATE.
* Cause ExecCountSlots() accounting to bear some relationship to reality.Tom Lane2001-05-27
| | | | Rather surprising we hadn't seen bug reports about this ...
* Fix eqjoinsel() to make use of new statistics.Tom Lane2001-05-27
|
* Make UPDATE and DELETE privileges distinct. Add REFERENCES and TRIGGERPeter Eisentraut2001-05-27
| | | | | privileges. INSERT and COPY FROM now require INSERT (only). Add privileges regression test.
* Add NUMERICOID return type. Treat it as floating point for now. ThisD'Arcy J.M. Cain2001-05-27
| | | | | could be changed if we create a new Python type that matches it better but NUMERIC <==> FLOAT probably works fine for most cases.
* Mention failure of ANT to delete directories on clean.Bruce Momjian2001-05-25
|
* See attached for a small patch that enables plpython to build cleanlyBruce Momjian2001-05-25
| | | | | | | | | | | | under Cygwin. This patch together with my previous Python patch: http://postgresql.readysetnet.com/mhonarc/pgsql-patches/2001-05/msg00075.htm l enables full Python support (i.e., configure --with-python) for Cygwin PostgreSQL. Jason Tishler
* Oops, only wanted python change in the last commit. Backing out.Bruce Momjian2001-05-25
|
* While changing Cygwin Python to build its core as a DLL (like Win32Bruce Momjian2001-05-25
| | | | | | | | | | | | | | | Python) to support shared extension modules, I have learned that Guido prefers the style of the attached patch to solve the above problem. I feel that this solution is particularly appropriate in this case because the following: PglargeType PgType PgQueryType are already being handled in the way that I am proposing for PgSourceType. Jason Tishler
* Back out, per Peter E.Bruce Momjian2001-05-25
| | | | | | | > > The attached patch changes src/interfaces/python/GNUmakefile to use the > > value of DESTDIR like the rest (or at least most) of the PostgreSQL > > makefiles. I found this problem when trying to package a pre-built > > Cygwin PostgreSQL distribution, but this problem is platform independent.
* The attached patch changes src/interfaces/python/GNUmakefile to use theBruce Momjian2001-05-25
| | | | | | | | | | | | | | | | | | | | value of DESTDIR like the rest (or at least most) of the PostgreSQL makefiles. I found this problem when trying to package a pre-built Cygwin PostgreSQL distribution, but this problem is platform independent. The problem manifests itself when one tries to install into a stagging area (e.g., to build a tarball) instead of a real install. In this case, pg.py and _pgmodule$(SO) still end up being installed in the configured prefix directory ignoring the value of DESTDIR. Unfortunately, this patch does not handle the case where PostgreSQL and Python are configured with different prefixes. Since the Python Makefile is automatically generated and does not use DESTDIR, I believe that this issue will be difficult to correct. If anyone has ideas on how to fix this issue, then I'm quite willing to rework the patch to take the suggestion into account. Jason Tishler
* The following patch corrects a make install problem when buildingBruce Momjian2001-05-25
| | | | | | | | | | | | under Cygwin. The root cause of this problem is that (Sun) java is a native Win32 app and hence does not understand Cygwin Posix style paths. The solution is to use Cygwin's cygpath utility to convert the Posix style JDBC installation directory path into a Win32 one before invoking ant. I'm not sure if my patch is the best way to correct this issue but my goal was to confine the Cygwin specific constructs to Jason Tishler
* Get rid of the following size limit.Hiroshi Inoue2001-05-25
| | | | | 1) Query size limit(was 65536) for >=7.0 servers. 2) Text size limit(was 8190) for 7.1 servers.
* Another Makefile fix for qnx patch.Bruce Momjian2001-05-25
|
* Fix tabs in Makefile.Bruce Momjian2001-05-25
|
* 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
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-07-16 00:45:03 +0000