- 27 8月, 1996 7 次提交
-
-
由 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 7 次提交
-
-
由 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 |
-
由 Marc G. Fournier 提交于
When you try to do any UPDATE of the catalog class pg_class, such as to change ownership of a class, the backend crashes. This is really two serial bugs: 1) there is a hardcoded copy of the schema of pg_class in the postgres program, and it doesn't match the actual class that initdb creates in the database; 2) Parts of postgres determine whether to pass an attribute value by value or by reference based on the attbyval attribute of the attribute in class pg_attribute. Other parts of postgres have it hardcoded. For the relacl[] attribute in class pg_class, attbyval does not match the hardcoded expectation. The fix is to correct the hardcoded schema for pg_attribute and to change the fetchatt macro so it ignores attbyval for all variable length attributes. The fix also adds a bunch of logic documentation and extends genbki.sh so it allows source files to contain such documentation. -- Bryan Henderson Phone 408-227-6803 San Jose, California
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
-
由 Julian Assange 提交于
-
- 20 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
-
- 19 8月, 1996 9 次提交
-
-
由 Marc G. Fournier 提交于
-
由 Marc G. Fournier 提交于
```yaml below my signature, there are a coupls of diffs and files in a shell archive, which were needed to build postgres95 1.02 on Siemens Nixdorfs MIPS based SINIX systems. Except for the compiler switches "-W0" and "-LD-Blargedynsym" these diffs should also apply for other SVR4 based systems. The changes in "Makefile.global" and "genbki.sh" can probably be ignored (I needed gawk, to make the script run). There is one bugfix thou. In "src/backend/parser/sysfunc.c" the function in this file didn't honor the EUROPEAN_DATES ifdef. ``` Submitted by: Frank Ridderbusch <ridderbusch.pad@sni.de>
-
由 Marc G. Fournier 提交于
-Kurt
-
由 Marc G. Fournier 提交于
-Kurt
-
由 Marc G. Fournier 提交于
Here's a couple more small fixes that I've made to make my runtime checker happy with the code. More along the lines of those that I sent in the past, ie, a pointer to an array != the name of an array. The last patch is that I mailed about yesterday -- I got two replies of "do it", so it's done. As far as I can tell, however, the function in question is never called by pg95, so either way it can't hurt... From: "Kurt J. Lidl" <lidl@va.pubnix.com>
-
由 Marc G. Fournier 提交于
When you connect to a database with PQsetdb, as with psql, depending on how your uninitialized variables are set, you can get a failure with a "There is no connection to the backend" message. The fix is to move a call to PQexec() from inside connectDB() to PQsetdb() after connectDB() returns to PQsetdb(). That way a connection doesn't have to be already established in order to establish it! From: bryanh@giraffe.netgate.net (Bryan Henderson)
-
由 Marc G. Fournier 提交于
fixed the spelling of 'nonexistent' in a few places...
-
由 Marc G. Fournier 提交于
| |This patch fixes a backend crash that happens sometimes when you try to |join on a field that contains NULL in some rows. Postgres tries to |compute a hash value of the field you're joining on, but when the field |is NULL, the pointer it thinks is pointing to the data is really just |pointing to random memory. This forces the hash value of NULL to be 0. | |It seems that nothing matches NULL on joins, even other NULL's (with or |without this patch). Is that what's supposed to happen? |
-
由 Marc G. Fournier 提交于
-
- 17 8月, 1996 1 次提交
-
-
由 Marc G. Fournier 提交于
Found/submittd by David Bennett
-
- 15 8月, 1996 4 次提交
-
-
由 Marc G. Fournier 提交于
Submitted by: Dan McGuirk <mcguirk@indirect.com>
-
由 Marc G. Fournier 提交于
CLUSTER command couldn't rename correctly the new created heap relation. The table base name resulted in some "temp_XXXX" instead of the correct base name. Submitted by: Dirk Koeser <koeser@informatik.uni-rostock.de>
-
由 Marc G. Fournier 提交于
Postgres is not able to cluster a relation on which an rtree index is defined. Postmaster gives the following error message: Too Large Allocation Request("!(0 < (size) && (size) <= (0xfffffff)):size=0 [0x0]", File:"/export/home/postgres/src/backend/utils/mmgr/mcxt.c", Line: 220) !(0 <(size) && (size) <= (0xfffffff)) (0) [No such file or directory] Submitted by: Dirk Koeser <koeser@informatik.uni-rostock.de>
-
由 Marc G. Fournier 提交于
|Here is a fix for the psql alignment problem. It turns out that libpq |was trying to determine if the column contained only numeric values so |it could right justify it. The 'e' values were taked as exponient |values and all columns were considered numeric. | |The patch excludes 'e' and 'E' as being valid first-column numeric |values. | Submitted by: Bruce...
-
- 14 8月, 1996 5 次提交
-
-
由 Marc G. Fournier 提交于
pg_dump and load to 2.0. I haven't gotten any feedback on whether people want it, so I am submitting it for others to decide. I would recommend an install in 1.02.1. I had said that the 2.0 pg_dump could dump a 1.02.1 database, but I was wrong. The copy is actually performed by the backend, and the 2.0 database will not be able to read 1.02.1 databases because of the new system columns. This patch does several things. It copies nulls out as \N, so they can be distinguished from '' strings. It fixes a problem where backslashes in the input stream were not output as double-backslashes. Without this patch, backslashes copied out were deleted upon input, or interpreted as special characters. Third, input is now terminated by backslash-period. This can not be part of a normal input stream. I tested this by creating a database with all sorts of nulls, backslash, and period fields and dumped the database and reloaded into a new database and compared them. Submitted by: Bruce
-
由 Marc G. Fournier 提交于
pg_dump and load to 2.0. I haven't gotten any feedback on whether people want it, so I am submitting it for others to decide. I would recommend an install in 1.02.1. I had said that the 2.0 pg_dump could dump a 1.02.1 database, but I was wrong. The copy is actually performed by the backend, and the 2.0 database will not be able to read 1.02.1 databases because of the new system columns. This patch does several things. It copies nulls out as \N, so they can be distinguished from '' strings. It fixes a problem where backslashes in the input stream were not output as double-backslashes. Without this patch, backslashes copied out were deleted upon input, or interpreted as special characters. Third, input is now terminated by backslash-period. This can not be part of a normal input stream. I tested this by creating a database with all sorts of nulls, backslash, and period fields and dumped the database and reloaded into a new database and compared them. Submitted by: Bruce
-
由 Marc G. Fournier 提交于
and found out that one of the patches is a show stopper for compiling under a strict ansi package. Please make sure the following fix makes it into the 1.02.1 release... Thanks. -Kurt
-
由 Marc G. Fournier 提交于
getting semaphore or shared memory errors. Submitted by: bryanh@giraffe.netgate.net (Bryan Henderson)
-
由 Marc G. Fournier 提交于
|We're all too familiar with psql's "no response from backend" message. |Users can't tell what this means, and psql continues prompting for |commands after it even though the backend is dead and no commands can |succeed. It eventually dies on a signal when the dead socket fills |up. I extended the message to offer a better explanation and made |psql exit when it finds the backend is dead. | |I also added a short message and newline when the user does a ctl-D so |it doesn't mess up the terminal display. | | Submitted by: Bryan Henderson <bryanh@giraffe.netgate.net>
-