summaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* Oops, wrong message with the other patch...this was the patch for the otherPG95-1_08Marc G. Fournier1996-10-041-1/+20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | comment, so here is the comment for the other patch *grin* > > You are right. I checked the gramar and saw the ability to use the > > parameter. I looked at the manual pages, and saw no reference to it. I > > tried running it, and found vacuum does nothing when you give it a table > > name. > > > > I checked a debug version of postgres, and the table name is passed to > > vacuum() in the variable (char *vacrel). The problem is that the vacuum > > spans transactions, and the vacrel name gets changed to '<vacuum>', > > which is the name of the portal that gets created in > > vacuum.c::_vc_vacuum(). vacuum.c::_vc_init() does a > > CommitTransactionCommand() which frees the memory allocated to vacrel. > > > > Should I change vacuum.c to copy the relation name to a local string > > variable of vacuum(), or do you recommend we allocate the table name in > > a different fashion? You are the man who knows the most about this. > > static NameData VacRel; Done. Attached is the patch. I have already applied it to the 2.0 tree. (Marc!) I tested it and it works. I also applied documentation patches to go with it. So now vacuum can be run for only one table if you wish. Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
* > - it excludes system-relation too (relkind == 's'). (Note: Vacuum updatesMarc G. Fournier1996-10-041-15/+25
| | | | | | | | | | | | | | | | | pg_class > by overwriting existing tuple for vacrel, so there are no many reasons to vacuum pg_class). > > It can be done somewhere in _vc_getrels - near to checks against archive relations > and relations on the write-once storage managers... > > Excuse me - I forgot to say about this. > Attached is the recently posted fix for this. Thanks. Submitted by: Bruce Momjian <maillist@candle.pha.pa.us>
* Here the fix for the first assertion failure I had which killedMarc G. Fournier1996-10-041-4/+5
| | | | | | | | | | my postmaster 1.07. It's really simple, the loop dealing with all sockets can't handle more than one ready socket :-) A simple logic error dealing with lists. OR IS THERE ANY REASON FOR SETTING curr TO 0? Submitted by: Carsten Heyl <Heyl@nads.de>
* Added spaces to end of QUERY lines so that createuser actually works...Marc G. Fournier1996-10-041-3/+3
|
* Quick fix required to fix SED script in postgres.shell.mkMarc G. Fournier1996-10-041-2/+4
| | | | V1.07
* change a reference to stdout to point to fout instead...Marc G. Fournier1996-10-021-3/+3
| | | | submitted by: Carsten Heyl <heyl@nads.de>
* From: "Kurt J. Lidl" <lidl@va.pubnix.com>Marc G. Fournier1996-10-021-2/+2
| | | | | To: pg95-dev@ki.net Subject: [PG95-DEV] array overrun in postmaster.c
* Added a fix for the dgux portMarc G. Fournier1996-10-021-1/+2
| | | | Pointed out by: "Brian E. Gallew" <geek+@cmu.edu>
* *** src/backend/storage/file/fd.c.orig Thu Sep 12 17:17:21 1996Marc G. Fournier1996-09-221-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | --- 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>
* Had EUROPEAN_DATES turned on by defaultMarc G. Fournier1996-09-211-2/+2
| | | | Pointed out by Bruce
* More declaration mis-match fixes...Marc G. Fournier1996-09-211-2/+6
|
* Now match the declaration in fe-auth.c to the one in fe-auth.h :)Marc G. Fournier1996-09-211-2/+2
|
* fix a conflicting declaration problem with fe_setauthsvc()...Marc G. Fournier1996-09-211-2/+2
|
* slight fix to Makefile.inc so that gram.c/parse.h get put intoMarc G. Fournier1996-09-211-3/+3
| | | | | | | backend/obj instead of into backend there is probably a better fix for this, but looking at the Makefile.inc, I can't find a reason *why* it isn't putting them into obj...
* POSTPORT should be 5432, not 6543Marc G. Fournier1996-09-211-3/+3
|
* Patches to make POSTPORT changes in scriptsMarc G. Fournier1996-09-216-11/+14
| | | | | Originally submitted by: ernst.molitor@uni-bonn.de resubmitted by: D'Arcy Cain
* This patch stops the Postgres build from ignoring the fact that yaccMarc G. Fournier1996-09-211-4/+4
| | | | | | | | has failed to create gram.c. -- Bryan Henderson Phone 408-227-6803 San Jose, California
* Hey, I didn't take it out, and its in the 2.0 source tree...*sigh*Marc G. Fournier1996-09-191-1/+2
|
* A fix for the pg_log bugMarc G. Fournier1996-09-191-26/+82
| | | | Submitted by: "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
* More sync ups...Marc G. Fournier1996-08-281-12/+16
|
* Another mis-sync...Marc G. Fournier1996-08-271-72/+114
|
* Somehow, we got out of sync hereMarc G. Fournier1996-08-271-16/+35
| | | | Pointed out by Bryan
* The following patch makes postmaster -D work. -D specifies a different PGDATAMarc G. Fournier1996-08-262-10/+12
| | | | | | | | | | | directory. The code that looks for the pg_hba file doesn't use it, though, so the postmaster uses the wrong pg_hba file. Also, when the postmaster looks in one directory and the user thinks it is looking in another directory, the error messages don't give enough information to solve the problem. I extended the error message for this. Submitted by: Bryan
* |The patch that is applied at the end of the email makes sure that theseMarc G. Fournier1996-08-261-8/+38
| | | | | | | | | | | |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>
* Take a chance that I'm correct:Marc G. Fournier1996-08-261-2/+2
| | | | | attno is used in an if statement, yet isn't defined, nor used anywhere else (~line 945)
* Fix the prototype for pg_dump's dumpClassesMarc G. Fournier1996-08-261-2/+3
|
* Fixed some commits that were missed dealing with Bryan's recentMarc G. Fournier1996-08-251-3/+44
| | | | patches
* This patch for Versions 1 and 2 corrects the following bug:Marc G. Fournier1996-08-241-5/+19
| | | | | | | | | | | | | | | | | | | | | 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-2413-83/+254
| | | | | | | | | | | | | | | | | | | 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-241-2/+2
| | | | | | | This presumably corrects a problem of initdb failing on systems that have an awk that is sensitive to this. Submitted by: bryanh@giraffe.netgate.net (Bryan Henderson)
* Changed genbki.sh block comment patch to avoid triggering an apparentDan McGuirk1996-08-221-2/+2
| | | | bug in GNU sed 3.0.
* |May I suggest to add access to the oid of an insertedMarc G. Fournier1996-08-211-1/+5
| | | | | | | | | | | | | | | |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 |
* Here is a patch for Versions 1 and 2 that corrects the following makefileMarc G. Fournier1996-08-213-7/+8
| | | | | | | | | | | | | bugs: 1) linker flags LDFLAGS are missing on some of the links. 2) libpq.a is not listed as a dependency for the src/bin programs that depend on it. -- Bryan Henderson Phone 408-227-6803 San Jose, California
* Here's a patch for Versions 1 and 2 that fixes the following bug:Marc G. Fournier1996-08-214-47/+97
| | | | | | | | | | | | | | | | | | | | | | | 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
* change gawk to awk ... creeped in from a previous patch..Marc G. Fournier1996-08-201-2/+2
|
* No wonder the Linux version kept screwing up...err() was fixed inMarc G. Fournier1996-08-201-2/+2
| | | | | | the wrong file... Pointed out by: Philip Plane <P.J.Plane@massey.ac.nz>
* iMarc G. Fournier1996-08-201-9/+13
| | | | | | Improvements to Makefiles to compensate for errors in compiling From: bryanh@giraffe.netgate.net (Bryan Henderson)
* iMarc G. Fournier1996-08-201-15/+12
| | | | | | Improvements to Makefiles to compensate for errors in compiling From: bryanh@giraffe.netgate.net (Bryan Henderson)
* Added a comment aruond the HISTORY_LIB/INC definesMarc G. Fournier1996-08-201-4/+6
|
* Furthre cleanup of -lreadline/-lhistoryMarc G. Fournier1996-08-201-5/+3
|
* Fix a bug with using READLINE that prevents psql from compilingMarc G. Fournier1996-08-201-6/+7
|
* BSD44_derived required -ltermcap as well...Marc G. Fournier1996-08-191-1/+5
|
* Change default of HISTORY_LIB so that it is disabled by defaultMarc G. Fournier1996-08-191-3/+3
|
* FreeBSD has libreadline,but not libhistory...Marc G. Fournier1996-08-191-2/+2
| | | | Change Makefile so that it can be commented out in Makefile.global
* Missed an else from Bryan's patch...Marc G. Fournier1996-08-191-2/+2
|
* Turn *off* TCL by defaultMarc G. Fournier1996-08-191-2/+2
|
* Make the doc directory a conditional...only try to "compile" if itMarc G. Fournier1996-08-191-2/+7
| | | | actually exists...
* The err() bug creeped back in again...Marc G. Fournier1996-08-191-6/+2
| | | | Pointed out by: brianc@saintjoe.edu
* Added a SVR4 portMarc G. Fournier1996-08-1913-30/+332
| | | | | | | | | | | | | | | | | | --- 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>
* Here's a minor fix that fixes a casting problem:Marc G. Fournier1996-08-191-2/+2
| | | | -Kurt
View Lorry Controller Status