postgresql - postgresql mirror

	Commit message (Collapse)	Author	Age
...
*	Allow VACUUM to complete faster by avoiding scanning the indexes when no	Bruce Momjian	2006-02-11
\| \| \| \| \| \|	rows were removed from the heap by the VACUUM. Simon Riggs
*	Re-run pgindent, fixing a problem where comment lines after a blank	Bruce Momjian	2005-11-22
\| \| \| \| \| \| \| \| \|	comment line where output as too long, and update typedefs for /lib directory. Also fix case where identifiers were used as variable names in the backend, but as typedefs in ecpg (favor the backend for indenting). Backpatch to 8.1.X.
*	Add simple sanity checks on newly-read pages to GiST, too.	Tom Lane	2005-11-06
\|
*	pgindent new GIST index code, per request from Tom.	Bruce Momjian	2005-09-22
\|
*	Adjust GiST error messages to conform to message style guidelines.	Tom Lane	2005-09-22
\|
*	Clean up a couple of ad-hoc computations of the maximum number of tuples	Tom Lane	2005-09-02
\| \| \| \| \| \| \| \| \| \| \|	on a page, as suggested by ITAGAKI Takahiro. Also, change a few places that were using some other estimates of max-items-per-page to consistently use MaxOffsetNumber. This is conservatively large --- we could have used the new MaxHeapTuplesPerPage macro, or a similar one for index tuples --- but those places are simply declaring a fixed-size buffer and assuming it will work, rather than actively testing for overrun. It seems safer to size these buffers in a way that can't overflow even if the page is corrupt.
*	Bug fixes for GiST crash recovery.	Teodor Sigaev	2005-06-30
\| \| \| \| \| \|	- add forgotten check of lsn for insert completion - remove level of pages: hard to check in recovery - some cleanups
*	Cleanup, remove unneeded pallocs	Teodor Sigaev	2005-06-29
\|
*	Code cleanup. gistfillbuffer accepts InvalidOffsetNumber.	Teodor Sigaev	2005-06-28
\|
*	Concurrency for GiST	Teodor Sigaev	2005-06-27
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	- full concurrency for insert/update/select/vacuum: - select and vacuum never locks more than one page simultaneously - select (gettuple) hasn't any lock across it's calls - insert never locks more than two page simultaneously: - during search of leaf to insert it locks only one page simultaneously - while walk upward to the root it locked only parent (may be non-direct parent) and child. One of them X-lock, another may be S- or X-lock - 'vacuum full' locks index - improve gistgetmulti - simplify XLOG records Fix bug in index_beginscan_internal: LockRelation may clean rd_aminfo structure, so move GET_REL_PROCEDURE after LockRelation
*	fix founded hole in recovery after crash, add vacuum_delay_point()	Teodor Sigaev	2005-06-20
\|
*	1. full functional WAL for GiST	Teodor Sigaev	2005-06-20
	2. improve vacuum for gist - use FSM - full vacuum: - reforms parent tuple if it's needed ( tuples was deleted on child page or parent tuple remains invalid after crash recovery ) - truncate index file if possible 3. fixes bugs and mistakes