- 16 9月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
| |Here's a patch for Version 2 only. It just adds an Assert to catch some |inconsistencies in the catalog classes. | |-- |Bryan Henderson Phone 408-227-6803 |San Jose, California |
-
- 10 9月, 1996 4 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
The problem is that the function arguments are not considered as possible key candidates for index scan and so only a sequential scan is possible inside the body of a function. I have therefore made some patches to the optimizer so that indices are now used also by functions. I have also moved the plan debug message from pg_eval to pg_plan so that it is printed also for plans genereated for function execution. I had also to add an index rescan to the executor because it ignored the parameters set in the execution state, they were flagged as runtime variables in ExecInitIndexScan but then never used by the executor so that the scan were always done with any key=1. Very odd. This means that an index rescan is now done twice for each function execution which uses an index, the first time when the index scan is initialized and the second when the actual function arguments are finally available for the execution. I don't know what is the cost of an double index scan but I suppose it is anyway less than the cost of a full sequential scan, at leat for large tables. This is my patch, you must also add -DINDEXSCAN_PATCH in Makefile.global to enable the changes. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
-
由 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 1 次提交
-
-
由 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
-