aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access
Commit message (Collapse)AuthorAge
* heapattr functions now return a Datum, not char *.Bruce Momjian1997-09-12
|
* Cleanup for array fix patch.Bruce Momjian1997-09-10
|
* Fix for arrays.Bruce Momjian1997-09-10
|
* Used modified version of indent that understands over 100 typedefs.Bruce Momjian1997-09-08
|
* Add typdefs to pgindent run.Bruce Momjian1997-09-08
|
* Another PGINDENT run that changes variable indenting and case label ↵Bruce Momjian1997-09-08
| | | | indenting. Also static variable indenting.
* Massive commit to run PGINDENT on all *.c and *.h files.Bruce Momjian1997-09-07
|
* TupleUpdatedByCurXactAndCmd () changed due toVadim B. Mikheev1997-08-29
| | | | | | Fix very old bug which made tuples changed/inserted by a commnd visible to command itself (so we had multiple update of updated tuples, etc).
* Fix very old bug which made tuples changed/inserted by a commndVadim B. Mikheev1997-08-29
| | | | | visible to command itself (so we had multiple update of updated tuples, etc).
* heap_delete returns int now (for non-functional deletes).Vadim B. Mikheev1997-08-27
|
* Inlined heap_getattr().Bruce Momjian1997-08-26
|
* Major patch to speed up backend startup after profiling analysis.Bruce Momjian1997-08-24
|
* Remove compile warning.Bruce Momjian1997-08-22
|
* CreateTupleDescCopy don't copy constraints now!Vadim B. Mikheev1997-08-22
| | | | | + CreateTupleDescCopyConstr to copy them too. + FreeTupleDesc
* Name change cleanup.Bruce Momjian1997-08-21
|
* AttrConstr --> TupleConstrVadim B. Mikheev1997-08-21
|
* Rename pg_attribute.attnvals to attdisbursion.Bruce Momjian1997-08-21
|
* Get rid of attproc, atttyparg, attcanindex, attdefrel, attboundVadim B. Mikheev1997-08-21
| | | | from pg_attribute. atthasdef added.
* More NOT_USEDsBruce Momjian1997-08-20
|
* HTNegate/HTCommute/HTNegateCommute are not used.Vadim B. Mikheev1997-08-20
|
* Make functions static where possible, enclose unused functions in #ifdef ↵Bruce Momjian1997-08-19
| | | | NOT_USED.
* NOT NULL implementation (submitted by Robson Paniago de Miranda).Vadim B. Mikheev1997-08-19
|
* Now that names are null terminated, no need to do all that NAMEDATALEN stuff.Bruce Momjian1997-08-18
|
* _hash_checkpage: cleanup for CASSERTVadim B. Mikheev1997-08-14
|
* These changes allow the module to compile quietly when assert checking isBruce Momjian1997-08-12
| | | | not being done.
* Remove more (void) and fix -Wall warnings.Bruce Momjian1997-08-12
|
* Catch non-functional delete attempts.Vadim B. Mikheev1997-08-06
|
* Cleanup for NAMEDATALEN use.Bruce Momjian1997-08-03
|
* _hash_first: release buf & metabuf if no tuples found for a key.Vadim B. Mikheev1997-06-28
|
* Someone forgot about aligning in fastgetiattr()...Vadim B. Mikheev1997-06-12
|
* Compare 'char' and 'text' lexicographically.Vadim B. Mikheev1997-06-11
|
* From: Robert Bruccoleri <bruc@bms.com>Marc G. Fournier1997-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | Subject: [PORTS] Patches for Irix 6.4 I have worked out how to compile PostgreSQL on Irix 6.4 using the -n32 compiler mode and version 7.1 of the C compiler. (The n32 compiler use 32 bits addressing, but allows access to all the instructions in the MIPS4 instruction set.) There were several problems: 1) The ld command is not referenced as a macro in all the Makefiles. On this platform, you have to include -n32 on all the ld commands. Makefiles were changed as needed. 3) Lots of warnings are generated from the compiler. Since the regression tests worked OK, I didn't attempt to fix them. If anyone wants the compilation log, please let me know, and I'll email it to you. The version of postgresql was 970602. Here is Makefile.custom: CUSTOM_COPT = -O2 -n32 MK_NO_LORDER = 1 LD = ld -n32 CC += -n32
* Duplicates handling...Vadim B. Mikheev1997-06-10
|
* Added check is new item successfuly inserted to a page or not.Vadim B. Mikheev1997-06-06
|
* If we have to split leaf page in the chain of duplicatesVadim B. Mikheev1997-05-31
| | | | | then we try to look at our right sibling first, but not farther, as it was in yesterday fix.
* Fix duplicates handling.Vadim B. Mikheev1997-05-30
|
* 1. Pass GISTENTRYs to giststate->penaltyFn by pointers, not by vals.Vadim B. Mikheev1997-05-22
| | | | 2. Re-initialize keys in gistrescan (if gist used in inner scan).
* From: Darren King <aixssd!darrenk@abs.net>Marc G. Fournier1997-05-22
| | | | | | | | | | Subject: [PATCHES] Re: [PORTS] AIX 6.1 fixes... Here are the patches for the two things that wouldn't make it thru the AIX compiler. The geo_ops.c change is harmless I believe. The nbtcompare.c patch fixes me, but I don't know about any other ports. Maybe wait on that one until Vadim decides what to do about the unsigned vs signed chars varlena issue.
* Initialize internal keys if rtree used in inner scan.Vadim B. Mikheev1997-05-20
|
* Bug: backend crashes in btbeginscan()->btrescan()->_bt_orderkeys()Vadim B. Mikheev1997-05-05
| | | | | | | | | when btree used in innerscan with run-time key which value passed by pointer. Fix: keys ordering stuff moved to _bt_first(). Pointed by Thomas Lockhart.
* Fix old bug in _hash_first() for scan without keys:Vadim B. Mikheev1997-04-30
| | | | if 1st bucket chain is empty then need to continue scan in the rest buckets.
* _bt_endpoint fixed: set currentItemData to Invalid if no result.Vadim B. Mikheev1997-04-24
|
* Major patch from Thomas Lockhart <Thomas.G.Lockhart@jpl.nasa.gov>Marc G. Fournier1997-04-22
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | OK, here are a passel of patches for the geometric data types. These add a "circle" data type, new operators and functions for the existing data types, and change the default formats for some of the existing types to make them consistant with each other. Current formatting conventions (e.g. compatible with v6.0 to allow dump/reload) are supported, but the new conventions should be an improvement and we can eventually drop the old conventions entirely. For example, there are two kinds of paths (connected line segments), open and closed, and the old format was '(1,2,1,2,3,4)' for a closed path with two points (1,2) and (3,4) '(0,2,1,2,3,4)' for an open path with two points (1,2) and (3,4) Pretty arcane, huh? The new format for paths is '((1,2),(3,4))' for a closed path with two points (1,2) and (3,4) '[(1,2),(3,4)]' for an open path with two points (1,2) and (3,4) For polygons, the old convention is '(0,4,2,0,4,3)' for a triangle with points at (0,0),(4,4), and (2,3) and the new convention is '((0,0),(4,4),(2,3))' for a triangle with points at (0,0),(4,4), and (2,3) Other data types which are also represented as lists of points (e.g. boxes, line segments, and polygons) have similar representations (they surround each point with parens). For v6.1, any format which can be interpreted as the old style format is decoded as such; we can remove that backwards compatibility but ugly convention for v7.0. This will allow dump/reloads from v6.0. These include some updates to the regression test files to change the test for creating a data type from "circle" to "widget" to keep the test from trashing the new builtin circle type.
* #ifdef BTREE_BUILD_STATS enables to get executor stats for btreeVadim B. Mikheev1997-04-18
| | | | building.
* Fix bttextcmp() to use unsigned char*.Vadim B. Mikheev1997-04-18
| | | | #ifdef USE_LOCALE added.
* 1. BTREE_VERSION_1: using bti_itup->t_tid as unique identifier for a givenVadim B. Mikheev1997-04-16
| | | | | | | | | | | | index tuple (logical position within A LEVEL). bti_oid & bti_dummy taken off from BTItemData. 2. Fix for multi-column indices (nbtsearch.c): _bt_binsrch() - for searches on internal pages having keysize < number of attrs we point at the last item < the scankey, not at the first item = the scankey; _bt_moveright() - if keysize < number of attrs we compare scankey with _last_ item on current page to decide should we move right or not.
* Fix btabstimecmp ().Vadim B. Mikheev1997-04-07
|
* CloseSequences () at xact commit/abort.Vadim B. Mikheev1997-04-02
|
* From: Dan McGuirk <mcguirk@indirect.com>Marc G. Fournier1997-03-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reply-To: hackers@hub.org, Dan McGuirk <mcguirk@indirect.com> To: hackers@hub.org Subject: [HACKERS] tmin writeback optimization I was doing some profiling of the backend, and noticed that during a certain benchmark I was running somewhere between 30% and 75% of the backend's CPU time was being spent in calls to TransactionIdDidCommit() from HeapTupleSatisfiesNow() or HeapTupleSatisfiesItself() to determine that changed rows' transactions had in fact been committed even though the rows' tmin values had not yet been set. When a query looks at a given row, it needs to figure out whether the transaction that changed the row has been committed and hence it should pay attention to the row, or whether on the other hand the transaction is still in progress or has been aborted and hence the row should be ignored. If a tmin value is set, it is known definitively that the row's transaction has been committed. However, if tmin is not set, the transaction referred to in xmin must be looked up in pg_log, and this is what the backend was spending a lot of time doing during my benchmark. So, implementing a method suggested by Vadim, I created the following patch that, the first time a query finds a committed row whose tmin value is not set, sets it, and marks the buffer where the row is stored as dirty. (It works for tmax, too.) This doesn't result in the boost in real time performance I was hoping for, however it does decrease backend CPU usage by up to two-thirds in certain situations, so it could be rather beneficial in high-concurrency settings.
* Someone forgot about 'case sizeof(int32)' forVadim B. Mikheev1997-03-26
| | | | tupleDesc->attrs[i]->attlen in fastgetiattr.
generated by cgit v1.2.3 (git 2.25.1) at 2025-08-06 09:51:43 +0000