- 10 9月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
The comparison routines for text and char data type give incorrect results if the input data contains characters greater than 127. As these routines perform the comparison using signed char variables all character codes greater than 127 are interpreted as less than 0. These codes are used to encode the iso8859 char sets. The other text-like data types seem to work as expected as they use unsigned chars in comparisons. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
-
由 Marc G. Fournier 提交于
Pointed out by: ernst.molitor@uni-bonn.de
-
- 29 8月, 1996 2 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
- 28 8月, 1996 16 次提交
-
-
由 Marc G. Fournier 提交于
- code compile tested, but due to a yet unresolved problem with parse.h's creation, compile not completed...
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
- centralizing to simplify the -I's required to compile
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
postgres.h already pulled in (postgres.h includes c.h)
-
由 Marc G. Fournier 提交于
in twice...
-
由 Marc G. Fournier 提交于
define to config.h
-
由 Marc G. Fournier 提交于
platform with a machine.h has the same BLCKSZ? Consolidate machine.h into config.h
-
由 Marc G. Fournier 提交于
#include "config.h" here will (should?) ensure that any platform dependencies defined in config.h should be reflected in all .c files...
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
First Step: Centralize them under on src/include hierarchy
-
- 27 8月, 1996 13 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
Goals: reduce the difficulty of porting from platform to platform, release to release, but moving as much as possible into config.h
-
由 Marc G. Fournier 提交于
to be one helluva chore to clean up...
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
tree, instead of having include files all over the place... Immediate goal...a 'config.h' file so that we can make #ifdef's being used throughout the code more a rarity as far as porting is concerned
-
由 Marc G. Fournier 提交于
include files *everywhere* ;(
-
由 Marc G. Fournier 提交于
conditions are always met. The patch can be applied to any version of Postgres95 from 1.02 to 1.05. After applying the patch, queries using indices on bpchar and varchar fields should (hopefully ;-) ) always return the same tuple set regardless to the fact whether indices are used or not. Submitted by: Gerhard Reithofer <tbr_laa@AON.AT>
-
由 Marc G. Fournier 提交于
the commit :( Here's the rest of the GiST code thta was missing...
-
由 Marc G. Fournier 提交于
-
- 26 8月, 1996 3 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
submitted by: Dan McGuirk
-
由 Marc G. Fournier 提交于
-
- 25 8月, 1996 3 次提交
-
-
由 Marc G. Fournier 提交于
In a catalog class that has a "name" type attribute, UPDATEing of an instance of that class may destroy all of the attributes of that instance that are stored as or after the "name" attribute. This is caused by the alignment value of the "name" type being set to "double" in Class pg_type, but "integer" in Class pg_attribute. Postgres constructs a tuple using double alignment, but interprets it using integer alignment. The fix is to change the alignment to integer in pg_type. Note that this corrects the problem for new Postgres systems. Existing databases already contain the error and it can't easily be repaired because this very bug prevents updating the class that contains it. -- Bryan Henderson Phone 408-227-6803 San Jose, California
-
由 Marc G. Fournier 提交于
It adds a WITH OIDS option to the copy command, which allows dumping and loading of oids. If a copy command tried to load in an oid that is greater than its current system max oid, the system max oid is incremented. No checking is done to see if other backends are running and have cached oids. pg_dump as its first step when using the -o (oid) option, will copy in a dummy row to set the system max oid value so as rows are loaded in, they are certain to be lower than the system oid. pg_dump now creates indexes at the end to speed loading Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
-
由 Marc G. Fournier 提交于
This presumably corrects a problem of initdb failing on systems that have an awk that is sensitive to this. -- Bryan Henderson Phone 408-227-6803 San Jose, California
-
- 21 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
|record, by a small patch to libpq++? At least until the |feature that will allow dumped oid's to be re-loaded into |a database becomes available, I need access to the oids |of newly created records... To this end, I have written a |three-line wrapper for the PQoidStatus function in libpq and |named this wrapper OidStatus() (I'd appreciate suggestions for |a name that would better fit into the general naming scheme). | |Regards, | |Ernst |
-