aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access
Commit message (Collapse)AuthorAge
* fix for index problem.Bruce Momjian1998-08-20
|
* heap_fetch requires buffer pointer, must be released; heap_getnextBruce Momjian1998-08-19
| | | | | | | | | | | | | no longer returns buffer pointer, can be gotten from scan; descriptor; bootstrap can create multi-key indexes; pg_procname index now is multi-key index; oidint2, oidint4, oidname are gone (must be removed from regression tests); use System Cache rather than sequential scan in many places; heap_modifytuple no longer takes buffer parameter; remove unused buffer parameter in a few other functions; oid8 is not index-able; remove some use of single-character variable names; cleanup Buffer variables usage and scan descriptor looping; cleaned up allocation and freeing of tuples; 18k lines of diff;
* fix typo.Bruce Momjian1998-08-11
|
* Strategy cleanups.Bruce Momjian1998-08-11
|
* index strategy cleanupBruce Momjian1998-08-11
|
* Update flowchart.Bruce Momjian1998-08-10
|
* Fix scan adjustment.Vadim B. Mikheev1998-07-30
|
* Use Snapshot in heap access methods.Vadim B. Mikheev1998-07-27
|
* From: t-ishii@sra.co.jpMarc G. Fournier1998-07-26
| | | | | | | | | As Bruce mentioned, this is due to the conflict among changes we made. Included patches should fix the problem(I changed all MB to MULTIBYTE). Please let me know if you have further problem. P.S. I did not include pathces to configure and gram.c to save the file size(configure.in and gram.y modified).
* VariableCache (next XID generator) is placed in shmem.Vadim B. Mikheev1998-07-21
|
* Theses buffer leaks are caused by indexes that are kept open betweenBruce Momjian1998-07-21
| | | | | | | | | | | | | | | | | | | | | calls. Outside a transaction, the backend detects them as buffer leaks; it sends a NOTICE, and frees them. This sometimes cause a segmentation fault (at least on Linux). These indexes are initialized on the first lo_read/lo_write/lo_tell call, and (normally) closed on a lo_close call. Thus the buffer leaks appear when lo direct access functions are used, and not with lo_import/lo_export functions (libpq version calls lo_close before ending the command, and the backend version uses another path). The included patches (against recent snapshot, and against 6.3.2) cause indexes to be closed on transaction end (that is on explicit 'END' statment, or on command termination outside trasaction blocks), thus preventing the buffer leaks while increasing performance inside transactions. Some (all?) 'classic' memory leaks are also removed. I hope it will be ok. --- Pascal ANDRE, graduated from Ecole Centrale Paris andre@via.ecp.fr
* Cleanup use of 16 that should be NAMEDATALEN.Bruce Momjian1998-07-20
|
* Cleanup Name usage.Bruce Momjian1998-07-20
|
* Add auto-size to screen to \d? commands. Use UNION to show allBruce Momjian1998-07-18
| | | | | \d? results in one query. Add \d? field search feature. Rename MB to MULTIBYTE.
* Change atttypmod from int16 to int32, for Thomas.Bruce Momjian1998-07-12
|
* Hi, here are the patches to enhance existing MB handling. This timeBruce Momjian1998-06-16
| | | | | | | | | | | | | | | | I have implemented a framework of encoding translation between the backend and the frontend. Also I have added a new variable setting command: SET CLIENT_ENCODING TO 'encoding'; Other features include: Latin1 support more 8 bit cleaness See doc/README.mb for more details. Note that the pacthes are against May 30 snapshot. Tatsuo Ishii
* Change error message and remove non-functional update message, fromBruce Momjian1998-06-16
| | | | Vadim.
* Remove un-needed braces around single statements.Bruce Momjian1998-06-15
|
* Fix macros that were not properly surrounded by parens or braces.Bruce Momjian1998-06-15
|
* Pass atttypmod to the frontend.Bruce Momjian1998-05-14
|
* Remove added NullProc define, and use fmgr.h value from fmgr.h.Bruce Momjian1998-05-13
|
* This patch...Bruce Momjian1998-04-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. Removes the unnecessary "#define AbcRegProcedure 123"'s from pg_proc.h. 2. Changes those #defines to use the names already defined in fmgr.h. 3. Forces the make of fmgr.h in backend/Makefile instead of having it made as a dependency in access/common/Makefile *hack*hack*hack* 4. Rearranged the #includes to a less helter-skelter arrangement, also changing <file.h> to "file.h" to signify a non-system header. 5. Removed "pg_proc.h" from files where its only purpose was for the #defines removed in item #1. 6. Added "fmgr.h" to each file changed for completeness sake. Turns out that #6 was not necessary for some files because fmgr.h was being included in a roundabout way SIX levels deep by the first include. "access/genam.h" ->"access/relscan.h" ->"utils/rel.h" ->"access/strat.h" ->"access/skey.h" ->"fmgr.h" So adding fmgr.h really didn't add anything to the compile, hopefully just made it clearer to the programmer. S Darren.
* Re-apply Darren's char2-16 removal code.Bruce Momjian1998-04-26
|
* Inline some small functions called for every row.Bruce Momjian1998-04-24
|
* Oops...I used Relation->rd_fd->relname exactly, instead of using the actualMarc G. Fournier1998-04-10
| | | | variable name *blush* *grin*
* Okay, add relation name to the file generating the error...Marc G. Fournier1998-04-10
|
* See if I can determine where the BTP_CHAIN error is coming from...Marc G. Fournier1998-04-10
|
* Back out char2-char16 removal. Add later.Bruce Momjian1998-04-07
|
* ASSERT fixes.Bruce Momjian1998-04-06
|
* Hi,Bruce Momjian1998-04-06
| | | | | | | | | | | | | | | | | | | | | | Attached you'll find a (big) patch that fixes make dep and make depend in all Makefiles where I found it to be appropriate. It also removes the dependency in Makefile.global for NAMEDATALEN and OIDNAMELEN by making backend/catalog/genbki.sh and bin/initdb/initdb.sh a little smarter. This no longer requires initdb.sh that is turned into initdb with a sed script when installing Postgres, hence initdb.sh should be renamed to initdb (after the patch has been applied :-) ) This patch is against the 6.3 sources, as it took a while to complete. Please review and apply, Cheers, Jeroen van Vianen
* The following uuencoded, gzip'd file will ...Bruce Momjian1998-03-30
| | | | | | | | | | | 1. Remove the char2, char4, char8 and char16 types from postgresql 2. Change references of char16 to name in the regression tests. 3. Rename the char16.sql regression test to name.sql. 4. Modify the regression test scripts and outputs to match up. Might require new regression.{SYSTEM} files... Darren King
* Fix scan adjusting for marked index tuples.Vadim B. Mikheev1998-02-28
|
* index_markpos()/index_restrpos are used now.Vadim B. Mikheev1998-02-26
|
* pgindent run before 6.3 release, with Thomas' requested changes.Bruce Momjian1998-02-26
|
* Change:Marc G. Fournier1998-02-21
| | | | | | | | | | | #define TAPETEMP "pg_btsortXXXXXX" to: #define TAPETEMP "pg_btsortXXXXXXX" For some reason, under FreeBSD, it appears that the mktemp() value needs the extra 'X' to improve/ensure uniqueness
* Goodbye register keyword. Compiler knows better.Bruce Momjian1998-02-11
|
* Pass around typmod as int16.Bruce Momjian1998-02-10
|
* Pass attypmod through to executor by adding to Var and Resdom.Bruce Momjian1998-02-10
|
* atttypmod now -1.Bruce Momjian1998-02-07
|
* Update now that attcacheoff initial value is -1 always.Bruce Momjian1998-02-06
|
* Fix for varchar functions, and indextyple j-1 fix.Bruce Momjian1998-02-05
|
* Symptom:Marc G. Fournier1998-02-05
| | | | | | | | select from a table with attrs (a int, b char(20)) crashed in bpcharout() (palloc of -1 bytes). But a table with attrs (a int, b varchar(20)) worked. From: Jan Wieck <jwieck@debis.com>
* char() cleanup and more cacheoff improvements.Bruce Momjian1998-02-05
|
* Cleanup getattr code. Make CHAR() use attcacheoff.Bruce Momjian1998-02-04
|
* fmgr_faddr cleanupBruce Momjian1998-01-31
|
* Inline fastgetattr and others so data access does not use functionBruce Momjian1998-01-31
| | | | calls.
* New pg_attribute.atttypmod for type-specific information likeBruce Momjian1998-01-16
| | | | | | | | | | | varchar length. Cleans up code so attlen is always length. Removed varchar() hack added earlier. Will fix bug in selecting varchar() fields, and varchar() can be variable length.
* Thank god for searchable mail archives.PostgreSQL Daemon1998-01-15
| | | | | | | | | Patch by: wieck@sapserv.debis.de (Jan Wieck) One of the design rules of PostgreSQL is extensibility. And to follow this rule means (at least for me) that there should not only be a builtin PL. Instead I would prefer a defined interface for PL implemetations.
* Some *very* major changes by darrenk@insightdist.com (Darren King)Marc G. Fournier1998-01-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | ========================================== What follows is a set of diffs that cleans up the usage of BLCKSZ. As a side effect, the person compiling the code can change the value of BLCKSZ _at_their_own_risk_. By that, I mean that I've tried it here at 4096 and 16384 with no ill-effects. A value of 4096 _shouldn't_ affect much as far as the kernel/file system goes, but making it bigger than 8192 can have severe consequences if you don't know what you're doing. 16394 worked for me, _BUT_ when I went to 32768 and did an initdb, the SCSI driver broke and the partition that I was running under went to hell in a hand basket. Had to reboot and do a good bit of fsck'ing to fix things up. The patch can be safely applied though. Just leave BLCKSZ = 8192 and everything is as before. It basically only cleans up all of the references to BLCKSZ in the code. If this patch is applied, a comment in the config.h file though above the BLCKSZ define with warning about monkeying around with it would be a good idea. Darren darrenk@insightdist.com (Also cleans up some of the #includes in files referencing BLCKSZ.) ==========================================
* Goodbye ABORT. Hello ERROR for all errors.Bruce Momjian1998-01-07
|
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-03 13:02:27 +0000