- 25 5月, 2001 8 次提交
-
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
> > 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.
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
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
-
由 Hiroshi Inoue 提交于
1) Query size limit(was 65536) for >=7.0 servers. 2) Text size limit(was 8190) for 7.1 servers.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 24 5月, 2001 9 次提交
-
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
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
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
- 23 5月, 2001 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
was lack of disk space. Oliver Elphick
-
由 Peter Eisentraut 提交于
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.
-
由 Peter Eisentraut 提交于
-
- 22 5月, 2001 10 次提交
-
-
由 Bruce Momjian 提交于
Klaus Reger
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
the output of "egrep '^[0-9]' " is empty. Changing the pattern to "egrep '^[ ]*[0-9]" generates the correct file. Tegge, Bernd
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
You can't use relation names alone in the target list, try relation.*
-
由 Bruce Momjian 提交于
-
由 Peter Eisentraut 提交于
too long. While I was adjusting the regression tests I moved the array things all into array.sql, to make things more manageable.
-
- 21 5月, 2001 2 次提交
-
-
由 Jan Wieck 提交于
- 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
-
由 Tom Lane 提交于
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!
-
- 20 5月, 2001 1 次提交
-
-
由 Bruce Momjian 提交于
-
- 19 5月, 2001 2 次提交
-
-
由 Peter Eisentraut 提交于
initialized FmgrInfo structs linger after elog.
-
由 Peter Eisentraut 提交于
FUNCTION command. Guard against trying to load a directory. Update documentation some.
-