aboutsummaryrefslogtreecommitdiff
path: root/src/backend
Commit message (Collapse)AuthorAge
* palloc() finfo memory. From Kurt.Bruce Momjian1996-09-26
|
* Fix cluster finfo problem Kurt reported.Bruce Momjian1996-09-26
|
* Fixed YACC depenencies and 'make clean' now cleans totally.Bruce Momjian1996-09-26
|
* This should cause 'make clean' to clean up bki files. Looks like a typo.Bruce Momjian1996-09-26
|
* Prevents possible packet loss from SIGCHLD.Bruce Momjian1996-09-26
|
* Changed gawk to awk.Bruce Momjian1996-09-25
|
* From: Bruce Momjian <maillist@candle.pha.pa.us>Marc G. Fournier1996-09-23
| | | | | | | | To: Postgres95-development <pg95-dev@ki.net> Subject: [PG95-DEV] postgres.h patch This removes the parameters from the func_ptr prototype in postgres.h in 2.0.
* diff -ru ../../../orig/postgres95/src/backend/utils/adt/varlena.cMarc G. Fournier1996-09-23
| | | | | | | | | | | | | | | | | | | ./utils/adt/varlena.c - --- ../../../orig/postgres95/src/backend/utils/adt/varlena.c Mon Jul 22 23:56:04 1996 +++ ./utils/adt/varlena.c Tue Sep 17 15:12:55 1996 @@ -166,7 +166,7 @@ if (inputText == NULL) return(NULL); - - len = strlen(inputText) + VARHDRSZ; + len = strlen(inputText) + VARHDRSZ + 1 /* terminating 0 */; result = (struct varlena *) palloc(len); VARSIZE(result) = len; memmove(VARDATA(result), inputText, len - VARHDRSZ); Submitted by: skimo@breughel.ufsia.ac.be (Sven Verdoolaege)
* diff -ru ../../../orig/postgres95/src/backend/libpq/be-fsstubs.cMarc G. Fournier1996-09-23
| | | | | | | | | | | | | | | | | | | | ./libpq/be-fsstubs.c - --- ../../../orig/postgres95/src/backend/libpq/be-fsstubs.c Tue Jul 9 08:21:30 1996 +++ ./libpq/be-fsstubs.c Tue Sep 17 15:30:09 1996 @@ -241,7 +241,7 @@ */ fd = open(VARDATA(filename), O_RDONLY, 0666); if (fd < 0) { /* error */ - - elog(WARN, "lo_import: can't open unix file\"%s\"\n", filename); + elog(WARN, "lo_import: can't open unix file \"%s\"\n", VARDATA(filename)); } /* Submited by: skimo@breughel.ufsia.ac.be (Sven Verdoolaege)
* Here's a patch that I discussed recently on pg95-dev that changes theMarc G. Fournier1996-09-23
| | | | | | | | | | | | way one creates a database system. Parts that were in "make install" are not either in "make all" or initdb. Nothing goes in the PGDATA directory besides user data. Creating multiple database systems is easier. In addition to applying the patch, it is necessary to move the file libpq/pg_hba to backend/libpq/pg_hba.sample. Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
* *** src/backend/storage/file/fd.c.orig Thu Sep 12 17:17:21 1996Marc G. Fournier1996-09-22
| | | | | | | | | | | | | | | | | | | | | | | | --- src/backend/storage/file/fd.c Thu Sep 12 17:23:38 1996 *************** *** 262,268 **** Delete(file); /* save the seek position */ ! fileP->seekPos = lseek(fileP->fd, 0L, SEEK_CUR); Assert( fileP->seekPos != -1); /* if we have written to the file, sync it */ --- 262,268 ---- Delete(file); /* save the seek position */ ! fileP->seekPos = (long) lseek(fileP->fd, 0L, SEEK_CUR); Assert( fileP->seekPos != -1); /* if we have written to the file, sync it */ Submitted by: Randy Terbush <randy@zyzzyva.com>
* |This fixes the bug introduced yesterday that causes "not found" errorsMarc G. Fournier1996-09-21
| | | | | | | | | |with gram.c and parser.h. | |-- |Bryan Henderson Phone 408-227-6803 |San Jose, California |
* Nothing patched...just testing something with CVS...Marc G. Fournier1996-09-21
|
* Various patches from Bryan that *should* clean up the compile problemsMarc G. Fournier1996-09-20
| | | | ppl are seeing with v2.0
* I have two small patches which correct some very obscure bug in the parserMarc G. Fournier1996-09-19
| | | | | | | of the array constants and in one of the loadable modules I posted some time ago. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
* Another small change. Added the void keyword to an empty arg list.Marc G. Fournier1996-09-19
| | | | Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
* Just a small change to flesh out the func_ptr typedef declaration.Marc G. Fournier1996-09-19
| | | | Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
* A few changes to cleanup the code.Marc G. Fournier1996-09-19
| | | | | | | | | | | | | | | | | | - Added the header access/heapam.h. - Changed all instances of "length" to "data_length" to quiet the compiler. - initialized a few variables. The compiler couldn't see that the code guaranteed that these would be initialized before being dereferenced. If anyone wants to check my work follow the usage of these variables and make sure that this true and wasn't actually a bug in the original code. - added a missing break statement to a default case. This was a benign error but bad style. - layed out heap_sysattrlen differently. I think this way makes the structure of the code crystal clear. There should be no actual difference in the actual behaviour of the code. Submitted by: darcy@druid.druid.com (D'Arcy J.M. Cain)
* Added querylimit patch...Marc G. Fournier1996-09-19
| | | | Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
* Fix for pg_log bugMarc G. Fournier1996-09-19
| | | | Submitted by: "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
* At Andrew's suggestion, upgrade the Version numbers to reflect theMarc G. Fournier1996-09-16
| | | | | | | | | | | | current state of development...namely, we are on 2.0 NOTE: BTW, the is also a check in postmaster which won't let you use an older version of the database by checking the version number. The version number of a database is in data/PG_VERSION (a plain ASCII file). - Andrew
* More code cleanups from "Kurt J. Lidl" <lidl@va.pubnix.com>Marc G. Fournier1996-09-16
|
* There is a bug in the function executor. The backend crashes while trying toMarc G. Fournier1996-09-16
| | | | | | | | | | execute an sql function containing an utility command (create, notify, ...). The bug is part in the planner, which returns a number of plans different than the number of commands if there are utility commands in the query, and in part in the function executor which assumes that all commands are normal query commands and causes a SIGSEGV trying to execute commands without plan. Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>
* |Subject: Postgres patch: Assert attribute type matchMarc G. Fournier1996-09-16
| | | | | | | | | | | | |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 |
* Fixes:Marc G. Fournier1996-09-10
| | | | | | | | | | | | | | | | | | | | | 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>
* Fixes:Marc G. Fournier1996-09-10
| | | | | | | | | | | | | 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>
* Cleaned up a spurious '-' ...Marc G. Fournier1996-09-10
| | | | Pointed out by: ernst.molitor@uni-bonn.de
* modifications required to reflect centralized include filesMarc G. Fournier1996-08-28
|
* Clean up th ecompile process by centralizing the include filesMarc G. Fournier1996-08-28
| | | | | - code compile tested, but due to a yet unresolved problem with parse.h's creation, compile not completed...
* Went back one directory too far for the -I includeMarc G. Fournier1996-08-28
|
* Path to pg_proc.h to create fmgrtab.c change to include/catalogMarc G. Fournier1996-08-28
|
* Moved the include files to src/include/regexMarc G. Fournier1996-08-28
|
* Should finish cleaning out the machine.h includesMarc G. Fournier1996-08-27
|
* Remove include of machine.hMarc G. Fournier1996-08-27
|
* Remove all traces of machine.h and redundant calls to c.h whereMarc G. Fournier1996-08-27
| | | | postgres.h already pulled in (postgres.h includes c.h)
* #include "postgres.h" exists in most .c files in system, so addingMarc G. Fournier1996-08-27
| | | | | #include "config.h" here will (should?) ensure that any platform dependencies defined in config.h should be reflected in all .c files...
* The use of include files is a mess...alot of redundancy, it seems...Marc G. Fournier1996-08-27
| | | | First Step: Centralize them under on src/include hierarchy
* added #include "config.h" for ESCAPE_PATCH defineMarc G. Fournier1996-08-27
|
* At this rate, maybe next year sometime I'll get this done...Marc G. Fournier1996-08-27
| | | | | Goals: reduce the difficulty of porting from platform to platform, release to release, but moving as much as possible into config.h
* first pass...move some of the "Port" dependencies to src/include/config.hMarc G. Fournier1996-08-27
|
* Create support for a "common" include directory for the sourceMarc G. Fournier1996-08-27
| | | | | | | | 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
* Damn, we really need to clean up this "include file" dilemna...Marc G. Fournier1996-08-26
| | | | include files *everywhere* ;(
* The patch that is applied at the end of the email makes sure that theseMarc G. Fournier1996-08-26
| | | | | | | | | | 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>
* Oops, thanks to Dan McGuirk for pointing out that I missed part ofMarc G. Fournier1996-08-26
| | | | | | the commit :( Here's the rest of the GiST code thta was missing...
* Quick fix of the PG-GiST import pointed out by DanMarc G. Fournier1996-08-26
|
* There, now we support GiST...now what? :)Marc G. Fournier1996-08-26
|
* Roll in patch that fixes problem with sed 3.0Marc G. Fournier1996-08-26
| | | | submitted by: Dan McGuirk
* This patch for Versions 1 and 2 corrects the following bug:Marc G. Fournier1996-08-24
| | | | | | | | | | | | | | | | | | | | | 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
* The patch does several things:Marc G. Fournier1996-08-24
| | | | | | | | | | | | | | | | | | | 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>
* Here's the fix for the problem that Evan Champion reported today.Marc G. Fournier1996-08-24
| | | | | | | | | 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