mirror of
				https://github.com/postgres/postgres.git
				synced 2025-11-03 09:13:20 +03:00 
			
		
		
		
	Minor improvements to the TODO list. Add some URLs for some
existing TODO items, and re-add a TODO item for an "estimated count" capability.
This commit is contained in:
		
							
								
								
									
										14
									
								
								doc/TODO
									
									
									
									
									
								
							
							
						
						
									
										14
									
								
								doc/TODO
									
									
									
									
									
								
							@@ -341,7 +341,7 @@ Functions
 | 
				
			|||||||
* Add ISO day of week format 'ID' to to_char() where Monday = 1
 | 
					* Add ISO day of week format 'ID' to to_char() where Monday = 1
 | 
				
			||||||
* Add a field 'isoyear' to extract(), based on the ISO week
 | 
					* Add a field 'isoyear' to extract(), based on the ISO week
 | 
				
			||||||
* Add SPI_gettypmod() to return the typemod for a TupleDesc
 | 
					* Add SPI_gettypmod() to return the typemod for a TupleDesc
 | 
				
			||||||
* Allow inlining of set-returning functions
 | 
					* Implement inlining of set-returning functions defined in SQL
 | 
				
			||||||
* Allow SQL-language functions to return results from RETURNING queries
 | 
					* Allow SQL-language functions to return results from RETURNING queries
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
@@ -928,6 +928,8 @@ Indexes
 | 
				
			|||||||
	  several hash buckets could be stored on a single page and greater
 | 
						  several hash buckets could be stored on a single page and greater
 | 
				
			||||||
	  granularity used for the hash algorithm.
 | 
						  granularity used for the hash algorithm.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
						  http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php
 | 
				
			||||||
 | 
					
 | 
				
			||||||
	o Consider sorting hash buckets so entries can be found using a
 | 
						o Consider sorting hash buckets so entries can be found using a
 | 
				
			||||||
	  binary search, rather than a linear scan
 | 
						  binary search, rather than a linear scan
 | 
				
			||||||
 | 
					
 | 
				
			||||||
@@ -972,6 +974,13 @@ Cache Usage
 | 
				
			|||||||
  faster than a sequential scan it must avoid access to the heap
 | 
					  faster than a sequential scan it must avoid access to the heap
 | 
				
			||||||
  to obtain tuple visibility information.
 | 
					  to obtain tuple visibility information.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					* Provide a way to calculate an "estimated COUNT(*)"
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					  Perhaps by using the optimizer's cardinality estimates or random
 | 
				
			||||||
 | 
					  sampling.
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					  http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php
 | 
				
			||||||
 | 
					
 | 
				
			||||||
* Allow data to be pulled directly from indexes
 | 
					* Allow data to be pulled directly from indexes
 | 
				
			||||||
 | 
					
 | 
				
			||||||
  Currently indexes do not have enough tuple visibility information 
 | 
					  Currently indexes do not have enough tuple visibility information 
 | 
				
			||||||
@@ -1075,6 +1084,9 @@ Locking
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
* Fix priority ordering of read and write light-weight locks (Neil)
 | 
					* Fix priority ordering of read and write light-weight locks (Neil)
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					  http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php
 | 
				
			||||||
 | 
					  http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
Startup Time Improvements
 | 
					Startup Time Improvements
 | 
				
			||||||
=========================
 | 
					=========================
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user