postgresql - postgresql mirror

	Commit message (Collapse)	Author	Age
...
*	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
*	WAL for GiST. It work for online backup and so on, but on	Teodor Sigaev	2005-06-14
	recovery after crash (power loss etc) it may say that it can't restore index and index should be reindexed. Some refactoring code.