TODO 54.2 KB
Newer Older
Bruce Momjian's avatar
Bruce Momjian committed
1

Bruce Momjian's avatar
Bruce Momjian committed
2 3
PostgreSQL TODO List
====================
Bruce Momjian's avatar
Bruce Momjian committed
4
Current maintainer:	Bruce Momjian (bruce@momjian.us)
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
5
Last updated:		Sat Jul  1 21:59:41 EDT 2006
Marc G. Fournier's avatar
Marc G. Fournier committed
6

Bruce Momjian's avatar
Bruce Momjian committed
7 8
The most recent version of this document can be viewed at
http://www.postgresql.org/docs/faqs.TODO.html.
Bruce Momjian's avatar
Bruce Momjian committed
9

Bruce Momjian's avatar
Bruce Momjian committed
10
#A hyphen, "-", marks changes that will appear in the upcoming 8.2 release.#
Bruce Momjian's avatar
Bruce Momjian committed
11
#A percent sign, "%", marks items that are easier to implement.#
12 13 14 15

Bracketed items, "[]", have more detail.

This list contains all known PostgreSQL bugs and feature requests. If
Bruce Momjian's avatar
Bruce Momjian committed
16
you would like to work on an item, please read the Developer's FAQ
17
first.
18

Bruce Momjian's avatar
Bruce Momjian committed
19

20 21
Administration
==============
Bruce Momjian's avatar
Bruce Momjian committed
22

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
23
* -Make postmater and postgres options distinct so the postmaster -o
Bruce Momjian's avatar
Bruce Momjian committed
24
  option is no longer needed
Bruce Momjian's avatar
Bruce Momjian committed
25
* -Allow pooled connections to list all prepared statements
26 27

  This would allow an application inheriting a pooled connection to know
28
  the statements prepared in the current session.
29

Bruce Momjian's avatar
Bruce Momjian committed
30 31
* Allow major upgrades without dump/reload, perhaps using pg_upgrade 
  [pg_upgrade]
Bruce Momjian's avatar
Bruce Momjian committed
32
* Check for unreferenced table files created by transactions that were
Bruce Momjian's avatar
Bruce Momjian committed
33
  in-progress when the server terminated abruptly
Bruce Momjian's avatar
Bruce Momjian committed
34 35 36

  http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php

Bruce Momjian's avatar
Bruce Momjian committed
37 38
* Allow administrators to safely terminate individual sessions either
  via an SQL function or SIGTERM 
39

Bruce Momjian's avatar
Bruce Momjian committed
40 41 42 43
  Lock table corruption following SIGTERM of an individual backend
  has been reported in 8.0.  A possible cause was fixed in 8.1, but
  it is unknown whether other problems exist.  This item mostly
  requires additional testing rather than of writing any new code.
44

Bruce Momjian's avatar
Bruce Momjian committed
45
* %Set proper permissions on non-system schemas during db creation
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
46

Bruce Momjian's avatar
Bruce Momjian committed
47 48
  Currently all schemas are owned by the super-user because they are
  copied from the template1 database.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
49

Bruce Momjian's avatar
Bruce Momjian committed
50 51 52
* Support table partitioning that allows a single table to be stored
  in subtables that are partitioned based on the primary key or a WHERE
  clause
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
53
* Add function to report the time of the most recent server reload
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
54 55 56
* Allow statistics collector information to be pulled from the collector
  process directly, rather than requiring the collector to write a
  filesystem file twice a second?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
57 58 59 60
* Allow log_min_messages to be specified on a per-module basis

  This would allow administrators to see more detailed information from
  specific sections of the backend, e.g. checkpoints, autovacuum, etc.
61 62
  Another idea is to allow separate configuration files for each module,
  or allow arbitrary SET commands to be passed to them.
Bruce Momjian's avatar
Bruce Momjian committed
63

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
64
* -Re-enable the GUC full_page_writes in 8.2 when reliability issues have
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
65 66
  been addressed

Bruce Momjian's avatar
Bruce Momjian committed
67

Bruce Momjian's avatar
Bruce Momjian committed
68
* Improve replication solutions
69

Bruce Momjian's avatar
Bruce Momjian committed
70
	o Load balancing
Bruce Momjian's avatar
Bruce Momjian committed
71

Bruce Momjian's avatar
Bruce Momjian committed
72 73 74
	  You can use any of the master/slave replication servers to use a
	  standby server for data warehousing. To allow read/write queries to
	  multiple servers, you need multi-master replication like pgcluster.
Bruce Momjian's avatar
Bruce Momjian committed
75

Bruce Momjian's avatar
Bruce Momjian committed
76
	o Allow replication over unreliable or non-persistent links
77 78


Bruce Momjian's avatar
Bruce Momjian committed
79
* Configuration files
80

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
81
	o -Add "include file" functionality in postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
82
	o %Allow commenting of variables in postgresql.conf to restore them
Bruce Momjian's avatar
Bruce Momjian committed
83
	  to defaults
Bruce Momjian's avatar
Bruce Momjian committed
84

Bruce Momjian's avatar
Bruce Momjian committed
85 86
	  Currently, if a variable is commented out, it keeps the
	  previous uncommented value until a server restarted.
Bruce Momjian's avatar
Bruce Momjian committed
87

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
88
	o -Allow per-database permissions to be set via GRANT
Bruce Momjian's avatar
Bruce Momjian committed
89

90 91
	  Allow database connection checks based on GRANT rules in
	  addition to the existing access checks in pg_hba.conf.
Bruce Momjian's avatar
Bruce Momjian committed
92

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
93 94 95 96 97 98 99 100 101
	o Allow pg_hba.conf to specify host names along with IP addresses

	  Host name lookup could occur when the postmaster reads the
	  pg_hba.conf file, or when the backend starts.  Another
	  solution would be to reverse lookup the connection IP and
	  check that hostname against the host names in pg_hba.conf.
	  We could also then check that the host name maps to the IP
	  address.

Bruce Momjian's avatar
Bruce Momjian committed
102
	o %Allow postgresql.conf file values to be changed via an SQL
Bruce Momjian's avatar
Bruce Momjian committed
103
	  API, perhaps using SET GLOBAL
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
104
	o Allow the server to be stopped/restarted via an SQL API
105
	o -Issue a warning if a change-on-restart-only postgresql.conf value
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
106 107
	  is modified  and the server config files are reloaded
	o Mark change-on-restart-only values in postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
108

109

Bruce Momjian's avatar
Bruce Momjian committed
110
* Tablespaces
111

Bruce Momjian's avatar
Bruce Momjian committed
112
	o Allow a database in tablespace t1 with tables created in
Bruce Momjian's avatar
Bruce Momjian committed
113 114
	  tablespace t2 to be used as a template for a new database created
	  with default tablespace t2
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
115

Bruce Momjian's avatar
Bruce Momjian committed
116 117 118 119 120 121 122 123
	  All objects in the default database tablespace must have default
	  tablespace specifications. This is because new databases are
	  created by copying directories. If you mix default tablespace
	  tables and tablespace-specified tables in the same directory,
	  creating a new database from such a mixed directory would create a
	  new database with tables that had incorrect explicit tablespaces.
	  To fix this would require modifying pg_class in the newly copied
	  database, which we don't currently do.
124

Bruce Momjian's avatar
Bruce Momjian committed
125
	o Allow reporting of which objects are in which tablespaces
126

Bruce Momjian's avatar
Bruce Momjian committed
127 128 129 130 131
	  This item is difficult because a tablespace can contain objects
	  from multiple databases. There is a server-side function that
	  returns the databases which use a specific tablespace, so this
	  requires a tool that will call that function and connect to each
	  database to find the objects in each database for that tablespace.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
132

Bruce Momjian's avatar
Bruce Momjian committed
133
	o %Add a GUC variable to control the tablespace for temporary objects
Bruce Momjian's avatar
Bruce Momjian committed
134
	  and sort files
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
135

Bruce Momjian's avatar
Bruce Momjian committed
136 137
	  It could start with a random tablespace from a supplied list and
	  cycle through the list.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
138

Bruce Momjian's avatar
Bruce Momjian committed
139 140
	o Allow WAL replay of CREATE TABLESPACE to work when the directory
	  structure on the recovery computer is different from the original
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
141

Bruce Momjian's avatar
Bruce Momjian committed
142
	o Allow per-tablespace quotas
143 144


145 146
* Point-In-Time Recovery (PITR)

Bruce Momjian's avatar
Bruce Momjian committed
147 148
	  o Allow point-in-time recovery to archive partially filled
	    write-ahead logs [pitr]
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
149

Bruce Momjian's avatar
Bruce Momjian committed
150 151 152 153 154 155 156 157 158
	    Currently only full WAL files are archived. This means that the
	    most recent transactions aren't available for recovery in case
	    of a disk failure. This could be triggered by a user command or
	    a timer.

	  o Automatically force archiving of partially-filled WAL files when
	    pg_stop_backup() is called or the server is stopped

	    Doing this will allow administrators to know more easily when
159
	    the archive contains all the files needed for point-in-time
160 161
	    recovery.  
	    http://archives.postgresql.org/pgsql-patches/2005-04/msg00121.php
Bruce Momjian's avatar
Bruce Momjian committed
162

Bruce Momjian's avatar
Bruce Momjian committed
163
	  o %Create dump tool for write-ahead logs for use in determining
Bruce Momjian's avatar
Bruce Momjian committed
164
	    transaction id for point-in-time recovery
165
	  o Allow a warm standby system to also allow read-only statements
Bruce Momjian's avatar
Bruce Momjian committed
166 167 168 169 170
	    [pitr]

	    This is useful for checking PITR recovery.

	  o Allow the PITR process to be debugged and data examined
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
171 172
	  o Add reporting of the current WAL file, perhaps as part of
	    partial log file archiving
Bruce Momjian's avatar
Bruce Momjian committed
173 174 175 176 177 178 179 180 181 182


Monitoring
==========

* Allow server log information to be output as INSERT statements

  This would allow server log information to be easily loaded into
  a database for analysis.

Bruce Momjian's avatar
Bruce Momjian committed
183
* %Add ability to monitor the use of temporary sort files
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
184
* -Allow server logs to be remotely read and removed using SQL commands
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
185
* Allow protocol-level BIND parameter values to be logged
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
186

Bruce Momjian's avatar
Bruce Momjian committed
187 188
  http://archives.postgresql.org/pgsql-hackers/2006-02/msg00165.php

Bruce Momjian's avatar
Bruce Momjian committed
189

190 191
Data Types
==========
192

Bruce Momjian's avatar
Bruce Momjian committed
193 194 195 196
* Improve the MONEY data type

  Change the MONEY data type to use DECIMAL internally, with special
  locale-aware output formatting.
Bruce Momjian's avatar
Bruce Momjian committed
197
  http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
Bruce Momjian's avatar
Bruce Momjian committed
198

199
* Change NUMERIC to enforce the maximum precision
Bruce Momjian's avatar
Bruce Momjian committed
200 201 202 203 204 205 206 207 208 209 210
* Add NUMERIC division operator that doesn't round?

  Currently NUMERIC _rounds_ the result to the specified precision.  
  This means division can return a result that multiplied by the 
  divisor is greater than the dividend, e.g. this returns a value > 10:

    SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6;

  The positive modulus result returned by NUMERICs might be considered
  inaccurate, in one sense.

211 212 213 214 215
* %Disallow changing DEFAULT expression of a SERIAL column?

  This should be done only if the existing SERIAL problems cannot be
  fixed.

Bruce Momjian's avatar
Bruce Momjian committed
216 217
* %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
  does not dump the changes
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
218
* Fix data types where equality comparison isn't intuitive, e.g. box
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
219 220
* -Zero umasked bits in conversion from INET cast to CIDR
* -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
221
* -Allow INET + INT8 to increment the host part of the address or
Bruce Momjian's avatar
Bruce Momjian committed
222
  throw an error on overflow
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
223
* -Add 'tid != tid ' operator for use in corruption recovery
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
224 225
* Allow user-defined types to specify a type modifier at table creation
  time
Bruce Momjian's avatar
Bruce Momjian committed
226
* Allow user-defined types to accept 'typmod' parameters
Bruce Momjian's avatar
Bruce Momjian committed
227

Bruce Momjian's avatar
Bruce Momjian committed
228 229
  http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php
  http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php
Bruce Momjian's avatar
Bruce Momjian committed
230

Bruce Momjian's avatar
>  
Bruce Momjian committed
231 232 233 234
* Add support for public SYNONYMs

  http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
235 236 237 238
* Fix CREATE CAST on DOMAINs

  http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php

Bruce Momjian's avatar
Bruce Momjian committed
239
* Add Globally/Universally Unique Identifier (GUID/UUID)
240 241
* Dates and Times

Bruce Momjian's avatar
Bruce Momjian committed
242
	o Allow infinite dates and intervals just like infinite timestamps
243 244 245 246 247 248 249 250
	o Merge hardwired timezone names with the TZ database; allow either 
	  kind everywhere a TZ name is currently taken
	o Allow customization of the known set of TZ names (generalize the
	  present australian_timezones hack)
	o Allow TIMESTAMP WITH TIME ZONE to store the original timezone
	  information, either zone name or offset from UTC [timezone]

	  If the TIMESTAMP value is stored with a time zone name, interval 
Bruce Momjian's avatar
Bruce Momjian committed
251
	  computations should adjust based on the time zone rules.
252

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
253
	o -Allow timezone names in SQL strings, '2006-05-24 21:11
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
254
	   Americas/New_York'::timestamptz
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
255
	o Fix SELECT '0.01 years'::interval, '0.01 months'::interval
Bruce Momjian's avatar
Bruce Momjian committed
256 257 258 259 260 261 262 263 264 265 266 267 268
	o Add a GUC variable to allow output of interval values in ISO8601 
	  format
	o Improve timestamptz subtraction to be DST-aware

	  Currently, subtracting one date from another that crosses a
	  daylight savings time adjustment can return '1 day 1 hour', but
	  adding that back to the first date returns a time one hour in
	  the future.  This is caused by the adjustment of '25 hours' to
	  '1 day 1 hour', and '1 day' is the same time the next day, even
	  if daylight savings adjustments are involved.

	o Fix interval display to support values exceeding 2^31 hours
	o Add overflow checking to timestamp and interval arithmetic	
269
	o Add ISO INTERVAL handling
270 271

		  http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php
Bruce Momjian's avatar
Bruce Momjian committed
272
		  http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php
273

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
274
		o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO 
275
		  SECOND
276 277 278
		o Support ISO INTERVAL syntax if units cannot be determined from
		  the string, and are supplied after the string

Bruce Momjian's avatar
Bruce Momjian committed
279 280 281 282 283
		  The SQL standard states that the units after the string
		  specify the units of the string, e.g. INTERVAL '2' MINUTE
		  should return '00:02:00'. The current behavior has the units
		  restrict the interval value to the specified unit or unit
		  range, INTERVAL '70' SECOND returns '00:00:10'.
284 285 286

		  For syntax that isn't uniquely ISO or PG syntax, like '1' or
		  '1:30', treat as ISO if there is a range specification clause,
Bruce Momjian's avatar
Bruce Momjian committed
287 288 289 290 291 292 293 294 295 296
		  and as PG if there no clause is present, e.g. interpret '1:30'
		  MINUTE TO SECOND as '1 minute 30 seconds', and interpret
		  '1:30' as '1 hour, 30 minutes'.

		  This makes common cases like SELECT INTERVAL '1' MONTH
		  SQL-standard results. The SQL standard supports a limited
		  number of unit combinations and doesn't support unit names in
		  the string. The PostgreSQL syntax is more flexible in the
		  range of units supported, e.g. PostgreSQL supports '1 year 1
		  hour', while the SQL standard does not.
297

298 299 300 301 302 303 304 305 306
		o Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
		o Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
		  INTERVAL MONTH), and this should return '12 months'
		o Round or truncate values to the requested precision, e.g.
		  INTERVAL '11 months' AS YEAR should return one or zero
		o Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))


* Arrays
Bruce Momjian's avatar
Bruce Momjian committed
307

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
308
	o -Allow NULLs in arrays
Bruce Momjian's avatar
Bruce Momjian committed
309 310
	o Delay resolution of array expression's data type so assignment
	  coercion can be performed on empty array expressions
Bruce Momjian's avatar
Bruce Momjian committed
311

Bruce Momjian's avatar
Bruce Momjian committed
312

313 314
* Binary Data

Bruce Momjian's avatar
Bruce Momjian committed
315
	o Improve vacuum of large objects, like /contrib/vacuumlo?
Bruce Momjian's avatar
Bruce Momjian committed
316
	o Add security checking for large objects
Bruce Momjian's avatar
Bruce Momjian committed
317
	o Auto-delete large objects when referencing row is deleted
318

Bruce Momjian's avatar
Bruce Momjian committed
319
          /contrib/lo offers this functionality.
320 321 322

	o Allow read/write into TOAST values like large objects

323
	  This requires the TOAST column to be stored EXTERNAL.
324

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
325 326 327 328
	o Add API for 64-bit large object access

	  http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php

329

Bruce Momjian's avatar
Bruce Momjian committed
330 331 332 333
Functions
=========

* Allow INET subnet tests using non-constants to be indexed
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
334
* -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
Bruce Momjian's avatar
Bruce Momjian committed
335 336 337 338 339 340 341
  functionality

  Current CURRENT_TIMESTAMP returns the start time of the current
  transaction, and gettimeofday() returns the wallclock time. This will
  make time reporting more consistent and will allow reporting of
  the statement start time.

Bruce Momjian's avatar
Bruce Momjian committed
342
* %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Bruce Momjian's avatar
Bruce Momjian committed
343
  pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
344
* -Allow to_char() to print localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
345
* Allow to_date() and to_timestamp() accept localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
346 347 348 349
* Add missing parameter handling in to_char()

	http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php

Bruce Momjian's avatar
Bruce Momjian committed
350 351 352 353 354 355 356 357 358 359 360 361 362 363 364
* Allow functions to have a schema search path specified at creation time
* Allow substring/replace() to get/set bit values
* Allow to_char() on interval values to accumulate the highest unit
  requested

  Some special format flag would be required to request such
  accumulation.  Such functionality could also be added to EXTRACT. 
  Prevent accumulation that crosses the month/day boundary because of
  the uneven number of days in a month.

	o to_char(INTERVAL '1 hour 5 minutes', 'MI') => 65
	o to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600 
	o to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
	o to_char(INTERVAL '3 years 5 months','MM') => 41

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
365
* -Add sleep() function, remove from regress.c
Bruce Momjian's avatar
Bruce Momjian committed
366
* -Allow user-defined functions retuning a domain value to enforce domain
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
367
  constraints
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
368
* Add SPI_gettypmod() to return the typemod for a TupleDesc
Bruce Momjian's avatar
Bruce Momjian committed
369

Bruce Momjian's avatar
Bruce Momjian committed
370

371 372
Multi-Language Support
======================
Bruce Momjian's avatar
Bruce Momjian committed
373

374
* Add NCHAR (as distinguished from ordinary varchar),
Bruce Momjian's avatar
Bruce Momjian committed
375
* Allow locale to be set at database creation
376

Bruce Momjian's avatar
Bruce Momjian committed
377 378 379 380
  Currently locale can only be set during initdb.  No global tables have
  locale-aware columns.  However, the database template used during
  database creation might have locale-aware indexes.  The indexes would
  need to be reindexed to match the new locale.
381 382 383

* Allow encoding on a per-column basis

384
  Right now only one encoding is allowed per database.  [locale]
385
  http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php
386

387
* Add CREATE COLLATE?  [locale]
Bruce Momjian's avatar
Bruce Momjian committed
388
* Support multiple simultaneous character sets, per SQL92
Bruce Momjian's avatar
Bruce Momjian committed
389
* Improve UTF8 combined character handling?
390 391
* Add octet_length_server() and octet_length_client()
* Make octet_length_client() the same as octet_length()?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
392
* Fix problems with wrong runtime encoding conversion for NLS message files
Bruce Momjian's avatar
Bruce Momjian committed
393 394 395
* Add URL to more complete multi-byte regression tests

  http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
396

Bruce Momjian's avatar
Bruce Momjian committed
397 398 399 400
* Fix ILIKE and regular expressions to handle case insensitivity
  properly in multibyte encodings

  http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php
401
  http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php
Bruce Momjian's avatar
Bruce Momjian committed
402

403

404 405
Views / Rules
=============
Bruce Momjian's avatar
Bruce Momjian committed
406

Neil Conway's avatar
Neil Conway committed
407
* Automatically create rules on views so they are updateable, per SQL99
Bruce Momjian's avatar
Bruce Momjian committed
408 409

  We can only auto-create rules for simple views.  For more complex
Neil Conway's avatar
Neil Conway committed
410
  cases users will still have to write rules manually.
Bruce Momjian's avatar
Bruce Momjian committed
411
  http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php
Bruce Momjian's avatar
Bruce Momjian committed
412

Bruce Momjian's avatar
Bruce Momjian committed
413
* Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
Bruce Momjian's avatar
Bruce Momjian committed
414
* Allow NOTIFY in rules involving conditionals
Bruce Momjian's avatar
Bruce Momjian committed
415
* Allow VIEW/RULE recompilation when the underlying tables change
416

Bruce Momjian's avatar
Bruce Momjian committed
417 418 419 420
  Another issue is whether underlying table changes should be reflected
  in the view, e.g. should SELECT * show additional columns if they
  are added after the view is created.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
421

422 423
SQL Commands
============
Bruce Momjian's avatar
Bruce Momjian committed
424

Bruce Momjian's avatar
Bruce Momjian committed
425
* Change LIMIT/OFFSET and FETCH/MOVE to use int8
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
426
* Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
427
* Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
Bruce Momjian's avatar
Bruce Momjian committed
428
* %Allow SET CONSTRAINTS to be qualified by schema/table name
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
429
* -Allow TRUNCATE ... CASCADE/RESTRICT
Bruce Momjian's avatar
Bruce Momjian committed
430 431 432

  This is like DELETE CASCADE, but truncates.

Bruce Momjian's avatar
Bruce Momjian committed
433
* %Add a separate TRUNCATE permission
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
434 435 436 437

  Currently only the owner can TRUNCATE a table because triggers are not
  called, and the table is locked in exclusive mode.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
438
* Allow PREPARE of cursors
Neil Conway's avatar
Neil Conway committed
439 440
* -Allow PREPARE to automatically determine parameter types based on the SQL
  statement (Neil)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
441 442 443 444 445 446 447 448
* Allow finer control over the caching of prepared query plans

  Currently, queries prepared via the libpq API are planned on first
  execute using the supplied parameters --- allow SQL PREPARE to do the
  same.  Also, allow control over replanning prepared queries either
  manually or automatically when statistics for execute parameters
  differ dramatically from those used during planning.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
449 450
* Invalidate prepared queries, like INSERT, when the table definition
  is altered
451 452 453 454 455
* Allow LISTEN/NOTIFY to store info in memory rather than tables?

  Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
  such information in memory would improve performance.

Bruce Momjian's avatar
Bruce Momjian committed
456
* Add optional textual message to NOTIFY
457 458 459 460 461

  This would allow an informational message to be added to the notify
  message, perhaps indicating the row modified or other custom
  information.

Bruce Momjian's avatar
Bruce Momjian committed
462
* Add a GUC variable to warn about non-standard SQL usage in queries
463
* Add SQL-standard MERGE command, typically used to merge two tables
Bruce Momjian's avatar
Bruce Momjian committed
464
  [merge]
465 466 467 468 469 470

  This is similar to UPDATE, then for unmatched rows, INSERT.
  Whether concurrent access allows modifications which could cause
  row loss is implementation independent.

* Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
Bruce Momjian's avatar
Bruce Momjian committed
471
  [merge]
Bruce Momjian's avatar
Bruce Momjian committed
472 473

  To implement this cleanly requires that the table have a unique index
474 475 476
  so duplicate checking can be easily performed.  It is possible to
  do it without a unique index if we require the user to LOCK the table
  before the MERGE.
Bruce Momjian's avatar
Bruce Momjian committed
477

Bruce Momjian's avatar
Bruce Momjian committed
478 479
* Add NOVICE output level for helpful messages like automatic sequence/index
  creation
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
480
* -Add COMMENT ON for all cluster global objects (roles, databases
Bruce Momjian's avatar
Bruce Momjian committed
481
  and tablespaces)
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
482
* -Make row-wise comparisons work per SQL spec
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
483 484 485 486 487

  Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but
  the SQL standard requires it to be processed as a column-by-column
  comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.

488
* Add RESET CONNECTION command to reset all session state
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
489

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
490
  This would include resetting of all variables (RESET ALL), dropping of
491 492 493 494
  temporary tables, removing any NOTIFYs, cursors, open transactions,
  prepared queries, currval()s, etc.  This could be used  for connection
  pooling.  We could also change RESET ALL to have this functionality.  
  The difficult of this features is allowing RESET ALL to not affect 
Bruce Momjian's avatar
Bruce Momjian committed
495 496
  changes made by the interface driver for its internal use.  One idea 
  is for this to be a protocol-only feature.  Another approach is to 
497
  notify the protocol when a RESET CONNECTION command is used.
Bruce Momjian's avatar
Bruce Momjian committed
498
  http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
499

500
* Add GUC to issue notice about statements that use unjoined tables
501
* Allow EXPLAIN to identify tables that were skipped because of 
502
  constraint_exclusion
503
* Allow EXPLAIN output to be more easily processed by scripts
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
504 505 506 507 508 509 510 511 512
* -Enable escape_string_warning and standard_conforming_strings
* Make standard_conforming_strings the default in 8.3?

  When this is done, backslash-quote should be prohibited in non-E''
  strings because of possible confusion over how such strings treat
  backslashes.  Basically, '' is always safe for a literal single
  quote, while \' might or might not be based on the backslash
  handling rules.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
513
* Simplify dropping roles that have objects in several databases
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
514
* Allow COMMENT ON to accept an expression rather than just a string
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
515 516
* Allow the count returned by SELECT, etc to be to represent as an int64
  to allow a higher range of values
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
517
* Make CLUSTER preserve recently-dead tuples per MVCC requirements
Bruce Momjian's avatar
Bruce Momjian committed
518
* Add SQL99 WITH clause to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
519
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
520 521 522 523
* Add DEFAULT .. AS OWNER so permission checks are done as the table
  owner

  This would be useful for SERIAL nextval() calls and CHECK constraints.
Bruce Momjian's avatar
Bruce Momjian committed
524

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
525 526 527
* Add a GUC to control whether BEGIN inside a transcation should abort
  the transaction.

Bruce Momjian's avatar
Bruce Momjian committed
528

529 530 531 532 533 534
* CREATE

	o Allow CREATE TABLE AS to determine column lengths for complex
	  expressions like SELECT col1 || col2
	o Use more reliable method for CREATE DATABASE to get a consistent
	  copy of db?
Neil Conway's avatar
Neil Conway committed
535
	o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT
536 537 538 539


* UPDATE
	o Allow UPDATE to handle complex aggregates [update]?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
540 541
	o -Allow an alias to be provided for the target table in
	  UPDATE/DELETE (Neil)
542 543 544 545
	o Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple
	  columns


Bruce Momjian's avatar
Bruce Momjian committed
546
* ALTER
547

Bruce Momjian's avatar
Bruce Momjian committed
548
	o %Have ALTER TABLE RENAME rename SERIAL sequence names
Bruce Momjian's avatar
Bruce Momjian committed
549
	o Add ALTER DOMAIN to modify the underlying data type
Bruce Momjian's avatar
Bruce Momjian committed
550
	o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
551

552
	  http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php
553

Bruce Momjian's avatar
Bruce Momjian committed
554
	o %Allow ALTER TABLE to change constraint deferrability and actions
Bruce Momjian's avatar
Bruce Momjian committed
555
	o Add missing object types for ALTER ... SET SCHEMA
556
	o Allow ALTER TABLESPACE to move to different directories
557
	o Allow databases to be moved to different tablespaces
558 559
	o Allow moving system tables to other tablespaces, where possible

560
	  Currently non-global system tables must be in the default database
561
	  tablespace. Global system tables can never be moved.
562

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
563
	o Prevent parent tables from altering or dropping constraints
564 565 566 567
	  like CHECK that are inherited by child tables unless CASCADE
	  is used
	o %Prevent child tables from altering or dropping constraints
          like CHECK that were inherited from the parent table
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
568
	o -Add ALTER TABLE tab INHERIT / NO INHERIT  parent
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
569
	o Have ALTER INDEX update the name of a constraint using that index
Bruce Momjian's avatar
Bruce Momjian committed
570
	o Add ALTER TABLE RENAME CONSTRAINT, update index name also
Bruce Momjian's avatar
Bruce Momjian committed
571

Bruce Momjian's avatar
Bruce Momjian committed
572

Bruce Momjian's avatar
Bruce Momjian committed
573
* CLUSTER
574

Bruce Momjian's avatar
Bruce Momjian committed
575
	o Automatically maintain clustering on a table
576

577 578
	  This might require some background daemon to maintain clustering
	  during periods of low usage. It might also require tables to be only
579
	  partially filled for easier reorganization.  Another idea would
580
          be to create a merged heap/index data file so an index lookup would
Bruce Momjian's avatar
Bruce Momjian committed
581
	  automatically access the heap data too.  A third idea would be to
Bruce Momjian's avatar
Bruce Momjian committed
582 583
	  store heap rows in hashed groups, perhaps using a user-supplied
	  hash function.
584

Bruce Momjian's avatar
Bruce Momjian committed
585
	o %Add default clustering to system tables
Bruce Momjian's avatar
Bruce Momjian committed
586

587 588
	  To do this, determine the ideal cluster index for each system
	  table and set the cluster setting during initdb.
589

Bruce Momjian's avatar
Bruce Momjian committed
590

Bruce Momjian's avatar
Bruce Momjian committed
591
* COPY
592

593
	o Allow COPY to report error lines and continue
594

595 596
	  This requires the use of a savepoint before each COPY line is
	  processed, with ROLLBACK on COPY failure.
597

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
598
	o -Have COPY return the number of rows loaded/unloaded?
Bruce Momjian's avatar
Bruce Momjian committed
599
	o Allow COPY on a newly-created table to skip WAL logging
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
600

Bruce Momjian's avatar
Bruce Momjian committed
601
	  On crash recovery, the table involved in the COPY would
Bruce Momjian's avatar
Bruce Momjian committed
602
	  be removed or have its heap and index files truncated.  One
Bruce Momjian's avatar
Bruce Momjian committed
603 604 605
	  issue is that no other backend should be able to add to 
	  the table at the same time, which is something that is 
	  currently allowed.
Bruce Momjian's avatar
Bruce Momjian committed
606

Bruce Momjian's avatar
Bruce Momjian committed
607
	o Allow COPY to output from SELECT
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
608

Bruce Momjian's avatar
Bruce Momjian committed
609
	  COPY should also be able to output views.
Bruce Momjian's avatar
Bruce Momjian committed
610
	  http://archives.postgresql.org/pgsql-patches/2005-09/msg00148.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
611

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
612

Bruce Momjian's avatar
Bruce Momjian committed
613
* GRANT/REVOKE
614

Bruce Momjian's avatar
Bruce Momjian committed
615
	o Allow column-level privileges
Bruce Momjian's avatar
Bruce Momjian committed
616
	o %Allow GRANT/REVOKE permissions to be applied to all schema objects
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
617
	  with one command
Bruce Momjian's avatar
Bruce Momjian committed
618 619 620 621 622

	  The proposed syntax is:
		GRANT SELECT ON ALL TABLES IN public TO phpuser;
		GRANT SELECT ON NEW TABLES IN public TO phpuser;

Bruce Momjian's avatar
Bruce Momjian committed
623
	o Allow GRANT/REVOKE permissions to be inherited by objects based on
Bruce Momjian's avatar
Bruce Momjian committed
624 625
	  schema permissions

Bruce Momjian's avatar
Bruce Momjian committed
626
	o Allow SERIAL sequences to inherit permissions from the base table?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
627

Bruce Momjian's avatar
Bruce Momjian committed
628

Bruce Momjian's avatar
Bruce Momjian committed
629
* CURSOR
630

631
	o Allow UPDATE/DELETE WHERE CURRENT OF cursor
632

633 634 635 636
	  This requires using the row ctid to map cursor rows back to the
	  original heap row. This become more complicated if WITH HOLD cursors
	  are to be supported because WITH HOLD cursors have a copy of the row
	  and no FOR UPDATE lock.
637 638

	o Prevent DROP TABLE from dropping a row referenced by its own open
Bruce Momjian's avatar
Bruce Momjian committed
639
	  cursor?
640

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
641
	o -Allow pooled connections to list all open WITH HOLD cursors
642

643 644
	  Because WITH HOLD cursors exist outside transactions, this allows
	  them to be listed so they can be closed.
Bruce Momjian's avatar
Bruce Momjian committed
645

Bruce Momjian's avatar
Bruce Momjian committed
646

Bruce Momjian's avatar
Bruce Momjian committed
647
* INSERT
648

649
	o Allow INSERT/UPDATE of the system-generated oid value for a row
Bruce Momjian's avatar
Bruce Momjian committed
650
	o Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
651
	o Allow INSERT/UPDATE ... RETURNING new.col or old.col
652

653 654
	  This is useful for returning the auto-generated key for an INSERT.
	  One complication is how to handle rules that run as part of
Bruce Momjian's avatar
Bruce Momjian committed
655 656
	  the insert.  
	  http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php
Bruce Momjian's avatar
Bruce Momjian committed
657

Bruce Momjian's avatar
Bruce Momjian committed
658

Bruce Momjian's avatar
Bruce Momjian committed
659
* SHOW/SET
660

Bruce Momjian's avatar
Bruce Momjian committed
661
	o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
Bruce Momjian's avatar
Bruce Momjian committed
662
	  ANALYZE, and CLUSTER
Bruce Momjian's avatar
Bruce Momjian committed
663
	o Add SET PATH for schemas?
664

665
	  This is basically the same as SET search_path.
Bruce Momjian's avatar
Bruce Momjian committed
666

Bruce Momjian's avatar
Bruce Momjian committed
667

Bruce Momjian's avatar
Bruce Momjian committed
668 669 670 671 672 673
* Referential Integrity

	o Add MATCH PARTIAL referential integrity
	o Change foreign key constraint for array -> element to mean element
	  in array?
	o Enforce referential integrity for system tables
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
674 675 676 677 678
	o Fix problem when cascading referential triggers make changes on
	  cascaded tables, seeing the tables in an intermediate state

	  http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
	  http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php
Bruce Momjian's avatar
Bruce Momjian committed
679 680


681 682
* Server-Side Languages

683 684 685
	o PL/pgSQL
		o Fix RENAME to work on variables other than OLD/NEW
		o Allow function parameters to be passed by name,
Bruce Momjian's avatar
Fix:  
Bruce Momjian committed
686
		  get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
687 688 689 690 691 692 693 694 695 696 697 698
		o Add Oracle-style packages
		o Allow handling of %TYPE arrays, e.g. tab.col%TYPE[]
		o Allow listing of record column names, and access to
		  record columns via variables, e.g. columns := r.(*),
		  tval2 := r.(colname)

		  http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php
		  http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php
		  http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php

		o Add MOVE
		o Add single-step debugging of functions
Bruce Momjian's avatar
Bruce Momjian committed
699 700 701 702 703
		o Add support for WITH HOLD and SCROLL cursors

		  PL/pgSQL cursors should support the same syntax as
		  backend cursors.

704 705 706 707
		o Allow PL/RETURN to return row or record functions

		  http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
708 709 710 711
		o Fix memory leak from exceptions

		  http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
712 713 714 715
		o Fix problems with RETURN NEXT on tables with
		  dropped/added columns after function creation

		  http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php
716 717 718 719 720 721 722 723

	o Other
		o Add table function support to pltcl, plpython
		o Add support for polymorphic arguments and return types to
		  languages other than PL/PgSQL
		o Add capability to create and call PROCEDURES
		o Add support for OUT and INOUT parameters to languages other 
		  than PL/PgSQL
Bruce Momjian's avatar
Bruce Momjian committed
724 725 726
		o Add PL/Python tracebacks

		  http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php
Bruce Momjian's avatar
Bruce Momjian committed
727

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
728 729 730 731
		o Allow PL/python to composite types and result sets
		  once buggy assert-enabled versions of python can be detected

		  http://archives.postgresql.org/pgsql-patches/2006-04/msg00087.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
732

733 734
Clients
=======
735

736
* -Have initdb set the input DateStyle (MDY or DMY) based on locale
737 738 739
* Have pg_ctl look at PGHOST in case it is a socket directory?
* Allow pg_ctl to work properly with configuration files located outside
  the PGDATA directory
740

741 742 743 744
  pg_ctl can not read the pid file because it isn't located in the
  config directory but in the PGDATA directory.  The solution is to
  allow pg_ctl to read and understand postgresql.conf to find the
  data_directory value.
745

746 747

* psql
Bruce Momjian's avatar
Bruce Momjian committed
748

749 750 751 752 753 754 755
	o Have psql show current values for a sequence
	o Move psql backslash database information into the backend, use
	  mnemonic commands? [psql]

	  This would allow non-psql clients to pull the same information out
	  of the database as psql.

Bruce Momjian's avatar
Bruce Momjian committed
756
	o Fix psql's \d commands more consistent
Bruce Momjian's avatar
Bruce Momjian committed
757 758

	  http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
Bruce Momjian's avatar
Bruce Momjian committed
759
	  http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php
Bruce Momjian's avatar
Bruce Momjian committed
760

761 762 763
	o Allow psql \pset boolean variables to set to fixed values, rather
	  than toggle
	o Consistently display privilege information for all objects in psql
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
764
	o -Improve psql's handling of multi-line statements
Bruce Momjian's avatar
Bruce Momjian committed
765

766 767
	  Currently, while \e saves a single statement as one entry, interactive
	  statements are saved one line at a time.  Ideally all statements
768
	  would be saved like \e does.
Bruce Momjian's avatar
Bruce Momjian committed
769

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
770
	o -Allow multi-line column values to align in the proper columns
Bruce Momjian's avatar
Bruce Momjian committed
771 772 773 774 775

	  If the second output column value is 'a\nb', the 'b' should appear
	  in the second display column, rather than the first column as it
	  does now.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
776 777 778 779 780
	o Display IN, INOUT, and OUT parameters in \df+

	  It probably requires psql to output newlines in the proper
	  column, which is already on the TODO list.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
781 782 783 784 785
	o Add auto-expanded mode so expanded output is used if the row
	  length is wider than the screen width.  

	  Consider using auto-expanded mode for backslash commands like \df+.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
786 787 788 789 790 791 792 793 794
	o Prevent tab completion of SET TRANSACTION from querying the
	  database and therefore preventing the transaction isolation
	  level from being set.

	  Currently, SET <tab> causes a database lookup to check all
	  supported session variables.  This query causes problems
	  because setting the transaction isolation level must be the
	  first statement of a transaction.

Bruce Momjian's avatar
Bruce Momjian committed
795

Bruce Momjian's avatar
Bruce Momjian committed
796
* pg_dump
797

798
	o %Allow pg_dump to use multiple -t and -n switches  [pg_dump]
Bruce Momjian's avatar
Bruce Momjian committed
799 800 801

	  http://archives.postgresql.org/pgsql-patches/2006-01/msg00190.php

Bruce Momjian's avatar
Bruce Momjian committed
802
	o %Add dumping of comments on index columns and composite type columns
Bruce Momjian's avatar
Bruce Momjian committed
803
	o %Add full object name to the tag field.  eg. for operators we need
Bruce Momjian's avatar
Bruce Momjian committed
804
	  '=(integer, integer)', instead of just '='.
Bruce Momjian's avatar
Bruce Momjian committed
805
	o Add pg_dumpall custom format dumps?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
806
	o -Update pg_dump and psql to use the new COPY libpq API (Christopher)
Bruce Momjian's avatar
Bruce Momjian committed
807 808
	o Remove unnecessary function pointer abstractions in pg_dump source
	  code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
809 810 811 812
	o Allow selection of individual object(s) of all types, not just
	  tables
	o In a selective dump, allow dumping of an object and all its 
	  dependencies
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
813
	o Add options like pg_restore -l and -L to pg_dump
Bruce Momjian's avatar
Bruce Momjian committed
814
	o Stop dumping CASCADE on DROP TYPE commands in clean mode
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
815 816
	o Allow pg_dump --clean to drop roles that own objects or have
	  privileges
Bruce Momjian's avatar
Bruce Momjian committed
817
	o Add -f to pg_dumpall
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
818

Bruce Momjian's avatar
Bruce Momjian committed
819

820 821
* ecpg

Michael Meskes's avatar
Michael Meskes committed
822
	o Docs
823

824 825
	  Document differences between ecpg and the SQL standard and
	  information about the Informix-compatibility module.
826

Bruce Momjian's avatar
Bruce Momjian committed
827
	o Solve cardinality > 1 for input descriptors / variables?
Bruce Momjian's avatar
Bruce Momjian committed
828
	o Add a semantic check level, e.g. check if a table really exists
Bruce Momjian's avatar
Bruce Momjian committed
829
	o fix handling of DB attributes that are arrays
Bruce Momjian's avatar
Bruce Momjian committed
830
	o Use backend PREPARE/EXECUTE facility for ecpg where possible
Bruce Momjian's avatar
Bruce Momjian committed
831
	o Implement SQLDA
Michael Meskes's avatar
Michael Meskes committed
832
	o Fix nested C comments
Bruce Momjian's avatar
Bruce Momjian committed
833
	o %sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified
834
	o Make SET CONNECTION thread-aware, non-standard?
835
	o Allow multidimensional arrays
Bruce Momjian's avatar
Bruce Momjian committed
836
	o Add internationalized message strings
Bruce Momjian's avatar
Bruce Momjian committed
837
	o Add COPY TO STDIN / STDOUT handling
Bruce Momjian's avatar
Bruce Momjian committed
838

Bruce Momjian's avatar
Bruce Momjian committed
839

Bruce Momjian's avatar
Bruce Momjian committed
840
* libpq
841 842

	o Add a function to support Parse/DescribeStatement capability
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
843
	o -Add PQescapeIdentifier()
844 845 846 847 848
	o Prevent PQfnumber() from lowercasing unquoted the column name

	  PQfnumber() should never have been doing lowercasing, but 
	  historically it has so we need a way to prevent it

849
	o Allow statement results to be automatically batched to the client
850

851
	  Currently, all statement results are transferred to the libpq
852 853
	  client before libpq makes the results available to the 
	  application.  This feature would allow the application to make
854
	  use of the first result rows while the rest are transferred, or
855
	  held on the server waiting for them to be requested by libpq.
856
	  One complexity is that a statement like SELECT 1/col could error
857 858 859
	  out mid-way through the result set.


Bruce Momjian's avatar
Bruce Momjian committed
860 861
Triggers
========
862 863 864 865 866 867
* Add deferred trigger queue file

  Right now all deferred trigger information is stored in backend
  memory.  This could exhaust memory for very large trigger queues.
  This item involves dumping large queues into files.

Bruce Momjian's avatar
Bruce Momjian committed
868
* Allow DEFERRABLE UNIQUE constraints?
869
* Allow triggers to be disabled in only the current session.
870

871 872 873
  This is currently possible by starting a multi-statement transaction,
  modifying the system tables, performing the desired SQL, restoring the
  system tables, and committing the transaction.  ALTER TABLE ...
Bruce Momjian's avatar
Bruce Momjian committed
874
  TRIGGER requires a table lock so it is not ideal for this usage.
875

876
* With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
877 878 879 880

  If the dump is known to be valid, allow foreign keys to be added
  without revalidating the data.

Bruce Momjian's avatar
Bruce Momjian committed
881
* Allow statement-level triggers to access modified rows
Bruce Momjian's avatar
Bruce Momjian committed
882 883
* Support triggers on columns

884
  http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php
Bruce Momjian's avatar
Bruce Momjian committed
885

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
886
* Allow AFTER triggers on system tables
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
887

888 889 890 891 892
  System tables are modified in many places in the backend without going
  through the executor and therefore not causing triggers to fire. To
  complete this item, the functions that modify system tables will have
  to fire triggers.

Bruce Momjian's avatar
Bruce Momjian committed
893

894 895
Dependency Checking
===================
Bruce Momjian's avatar
Bruce Momjian committed
896

Bruce Momjian's avatar
Bruce Momjian committed
897 898 899
* Flush cached query plans when the dependent objects change,
  when the cardinality of parameters changes dramatically, or
  when new ANALYZE statistics are available
Bruce Momjian's avatar
Bruce Momjian committed
900 901 902 903

  A more complex solution would be to save multiple plans for different
  cardinality and use the appropriate plan based on the EXECUTE values.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
904
* Track dependencies in function bodies and recompile/invalidate
905

Bruce Momjian's avatar
Bruce Momjian committed
906 907
  This is particularly important for references to temporary tables
  in PL/PgSQL because PL/PgSQL caches query plans.  The only workaround
908 909 910
  in PL/PgSQL is to use EXECUTE.  One complexity is that a function
  might itself drop and recreate dependent tables, causing it to
  invalidate its own query plan.
Bruce Momjian's avatar
Bruce Momjian committed
911

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
912

913 914
Exotic Features
===============
915

Bruce Momjian's avatar
Bruce Momjian committed
916
* Add pre-parsing phase that converts non-ISO syntax to supported
917 918 919 920 921
  syntax

  This could allow SQL written for other databases to run without
  modification.

Bruce Momjian's avatar
Bruce Momjian committed
922
* Allow plug-in modules to emulate features from other databases
Bruce Momjian's avatar
Bruce Momjian committed
923
* SQL*Net listener that makes PostgreSQL appear as an Oracle database
Bruce Momjian's avatar
Bruce Momjian committed
924
  to clients
925
* Allow statements across databases or servers with transaction
926
  semantics
927

928
  This can be done using dblink and two-phase commit.
929

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
930
* Add the features of packages
931

932
	o  Make private objects accessible only to objects in the same schema
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
933 934 935
	o  Allow current_schema.objname to access current schema objects
	o  Add session variables
	o  Allow nested schemas
936

Bruce Momjian's avatar
Bruce Momjian committed
937 938 939
* Consider allowing control of upper/lower case folding of unquoted
  identifiers

940
  http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php
Bruce Momjian's avatar
Bruce Momjian committed
941

Bruce Momjian's avatar
Bruce Momjian committed
942 943 944 945 946 947 948 949 950 951 952 953
Indexes
=======

* Allow inherited tables to inherit index, UNIQUE constraint, and primary
  key, foreign key
* UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
  inherited table:  INSERT INTO inherit_table (unique_index_col) VALUES
  (dup) should fail

  The main difficulty with this item is the problem of creating an index
  that can span more than one table.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
954
* Allow SELECT ... FOR UPDATE on inherited tables
Bruce Momjian's avatar
Bruce Momjian committed
955 956 957 958 959 960 961 962 963 964 965 966
* Add UNIQUE capability to non-btree indexes
* Prevent index uniqueness checks when UPDATE does not modify the column

  Uniqueness (index) checks are done when updating a column even if the
  column is not modified by the UPDATE.

* Allow the creation of on-disk bitmap indexes which can be quickly
  combined with other bitmap indexes

  Such indexes could be more compact if there are only a few distinct values.
  Such indexes can also be compressed.  Keeping such indexes updated can be
  costly.
Bruce Momjian's avatar
Bruce Momjian committed
967
  http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
Bruce Momjian's avatar
Bruce Momjian committed
968 969 970 971 972 973 974 975

* Allow use of indexes to search for NULLs

  One solution is to create a partial index on an IS NULL expression.

* Allow accurate statistics to be collected on indexes with more than
  one column or expression indexes, perhaps using per-index statistics
* Add fillfactor to control reserved free space during index creation
Bruce Momjian's avatar
Bruce Momjian committed
976 977 978 979 980 981 982 983
* Allow the creation of indexes with mixed ascending/descending
  specifiers

  This is possible now by creating an operator class with reversed sort
  operators.  One complexity is that NULLs would then appear at the start
  of the result set, and this might affect certain sort types, like
  merge join.

984
* Allow constraint_exclusion to work for UNIONs like it does for
985 986
  inheritance, allow it to work for UPDATE and DELETE statements, and allow
  it to be used for all statements with little performance impact
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
987 988
* Allow CREATE INDEX to take an additional parameter for use with
  special index types
Bruce Momjian's avatar
Bruce Momjian committed
989
* Consider compressing indexes by storing key values duplicated in
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
990
  several rows as a single index entry
Bruce Momjian's avatar
Bruce Momjian committed
991

Bruce Momjian's avatar
Bruce Momjian committed
992 993
  This is difficult because it requires datatype-specific knowledge.

Bruce Momjian's avatar
Bruce Momjian committed
994

995 996 997 998 999
* GIST

	o Add more GIST index support for geometric data types
	o Allow GIST indexes to create certain complex index types, like
	  digital trees (see Aoki)
Bruce Momjian's avatar
Bruce Momjian committed
1000 1001

* Hash
1002

Bruce Momjian's avatar
Bruce Momjian committed
1003 1004
	o Pack hash index buckets onto disk pages more efficiently

Bruce Momjian's avatar
Bruce Momjian committed
1005
	  Currently only one hash bucket can be stored on a page. Ideally
Bruce Momjian's avatar
Bruce Momjian committed
1006 1007 1008 1009 1010 1011 1012 1013
	  several hash buckets could be stored on a single page and greater
	  granularity used for the hash algorithm.

	o Consider sorting hash buckets so entries can be found using a
	  binary search, rather than a linear scan

	o In hash indexes, consider storing the hash value with or instead
	  of the key itself
1014

Bruce Momjian's avatar
Bruce Momjian committed
1015 1016 1017
	o Add WAL logging for crash recovery
	o Allow multi-column hash indexes

1018

1019 1020
Fsync
=====
1021

1022
* Improve commit_delay handling to reduce fsync()
Bruce Momjian's avatar
Bruce Momjian committed
1023
* Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Bruce Momjian's avatar
Bruce Momjian committed
1024 1025

  Ideally this requires a separate test program that can be run
Bruce Momjian's avatar
Bruce Momjian committed
1026 1027
  at initdb time or optionally later.  Consider O_SYNC when
  O_DIRECT exists.
Bruce Momjian's avatar
Bruce Momjian committed
1028

Bruce Momjian's avatar
Bruce Momjian committed
1029
* %Add an option to sync() before fsync()'ing checkpoint files
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1030
* Add program to test if fsync has a delay compared to non-fsync
Bruce Momjian's avatar
Bruce Momjian committed
1031

1032

Bruce Momjian's avatar
Bruce Momjian committed
1033 1034
Cache Usage
===========
Bruce Momjian's avatar
Bruce Momjian committed
1035

Bruce Momjian's avatar
Bruce Momjian committed
1036
* Allow free-behind capability for large sequential scans, perhaps using
Bruce Momjian's avatar
Bruce Momjian committed
1037 1038
  posix_fadvise()

Bruce Momjian's avatar
Bruce Momjian committed
1039
  Posix_fadvise() can control both sequential/random file caching and
Bruce Momjian's avatar
Bruce Momjian committed
1040 1041 1042 1043
  free-behind behavior, but it is unclear how the setting affects other
  backends that also have the file open, and the feature is not supported
  on all operating systems.

1044 1045 1046 1047
* Speed up COUNT(*)

  We could use a fixed row count and a +/- count to follow MVCC
  visibility rules, or a single cached value could be used and
1048 1049 1050 1051 1052
  invalidated if anyone modifies the table.  Another idea is to
  get a count directly from a unique index, but for this to be
  faster than a sequential scan it must avoid access to the heap
  to obtain tuple visibility information.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1053 1054
* Add estimated_count(*) to return an estimate of COUNT(*)

1055
  This would use the planner ANALYZE statistics to return an estimated
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1056 1057
  count.

1058 1059
* Allow data to be pulled directly from indexes

Bruce Momjian's avatar
Bruce Momjian committed
1060 1061
  Currently indexes do not have enough tuple visibility information 
  to allow data to be pulled from the index without also accessing 
1062
  the heap.  One way to allow this is to set a bit on index tuples 
Bruce Momjian's avatar
Bruce Momjian committed
1063 1064
  to indicate if a tuple is currently visible to all transactions 
  when the first valid heap lookup happens.  This bit would have to 
1065 1066 1067 1068 1069 1070 1071 1072
  be cleared when a heap tuple is expired.  

  Another idea is to maintain a bitmap of heap pages where all rows
  are visible to all backends, and allow index lookups to reference 
  that bitmap to avoid heap lookups, perhaps the same bitmap we might
  add someday to determine which heap pages need vacuuming.  Frequently
  accessed bitmaps would have to be stored in shared memory.  One 8k
  page of bitmaps could track 512MB of heap pages.
Bruce Momjian's avatar
Bruce Momjian committed
1073

1074
* Consider automatic caching of statements at various levels:
Bruce Momjian's avatar
Bruce Momjian committed
1075

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1076 1077 1078 1079
	o Parsed query tree
	o Query execute plan
	o Query results

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1080
* Allow sequential scans to take advantage of other concurrent
1081
  sequential scans, also called "Synchronised Scanning"
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1082

1083 1084 1085 1086
  One possible implementation is to start sequential scans from the lowest
  numbered buffer in the shared cache, and when reaching the end wrap
  around to the beginning, rather than always starting sequential scans
  at the start of the table.
Bruce Momjian's avatar
Bruce Momjian committed
1087

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1088 1089 1090 1091
* Consider increasing internal areas when shared buffers is increased

  http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php

Bruce Momjian's avatar
Bruce Momjian committed
1092

1093 1094
Vacuum
======
Bruce Momjian's avatar
Bruce Momjian committed
1095

1096 1097
* Improve speed with indexes

1098
  For large table adjustments during VACUUM FULL, it is faster to 
Bruce Momjian's avatar
Bruce Momjian committed
1099
  reindex rather than update the index.
1100

Bruce Momjian's avatar
Bruce Momjian committed
1101 1102
* Reduce lock time during VACUUM FULL by moving tuples with read lock,
  then write lock and truncate table
1103 1104 1105 1106 1107

  Moved tuples are invisible to other backends so they don't require a
  write lock. However, the read lock promotion to write lock could lead
  to deadlock situations.

Bruce Momjian's avatar
Bruce Momjian committed
1108 1109
* Auto-fill the free space map by scanning the buffer cache or by
  checking pages written by the background writer
1110 1111

  http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php
Bruce Momjian's avatar
Bruce Momjian committed
1112
  http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php
1113

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1114 1115 1116 1117 1118 1119
* Create a bitmap of pages that need vacuuming

  Instead of sequentially scanning the entire table, have the background
  writer or some other process record pages that have expired rows, then
  VACUUM can look at just those pages rather than the entire table.  In
  the event of a system crash, the bitmap would probably be invalidated.
Bruce Momjian's avatar
Bruce Momjian committed
1120 1121 1122 1123
  One complexity is that index entries still have to be vacuumed, and
  doing this without an index scan (by using the heap values to find the
  index entry) might be slow and unreliable, especially for user-defined
  index functions.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1124

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1125
* -Add system view to show free space map contents
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1126 1127
* Allow FSM to return free space toward the beginning of the heap file,
  in hopes that empty pages at the end can be truncated by VACUUM
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1128 1129
* Allow FSM page return free space based on table clustering, to assist
  in maintaining clustering?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1130
* Consider shrinking expired tuples to just their headers
Bruce Momjian's avatar
Bruce Momjian committed
1131

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1132
  http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php
Bruce Momjian's avatar
Bruce Momjian committed
1133

Bruce Momjian's avatar
Bruce Momjian committed
1134 1135
* Allow heap reuse of UPDATEd rows if no indexed columns are changed,
  and old and new versions are on the same heap page?
1136

Bruce Momjian's avatar
Bruce Momjian committed
1137 1138 1139 1140
  While vacuum handles DELETEs fine, updating of non-indexed columns, like
  counters, are difficult for VACUUM to handle efficiently.  This method
  is possible for same-page updates because a single index row can be
  used to point to both old and new values.
1141
  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
Bruce Momjian's avatar
Bruce Momjian committed
1142
  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php
1143

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1144 1145
* Reuse index tuples that point to heap tuples that are not visible to 
  anyone?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1146
* Auto-vacuum
1147

Bruce Momjian's avatar
Bruce Momjian committed
1148
	o Use free-space map information to guide rfilling
Bruce Momjian's avatar
Bruce Momjian committed
1149 1150
	o %Issue log message to suggest VACUUM FULL if a table is nearly
	  empty?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1151 1152
	o Improve xid wraparound detection by recording per-table rather
	  than per-database
Bruce Momjian's avatar
Bruce Momjian committed
1153
	o Consider logging activity either to the logs or a system view
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1154

Bruce Momjian's avatar
Bruce Momjian committed
1155

1156 1157
Locking
=======
1158

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1159
* Fix priority ordering of read and write light-weight locks (Neil)
1160

1161

Bruce Momjian's avatar
Bruce Momjian committed
1162 1163
Startup Time Improvements
=========================
1164

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1165
* Experiment with multi-threaded backend for backend creation [thread]
1166 1167 1168

  This would prevent the overhead associated with process creation. Most
  operating systems have trivial process creation time compared to
1169
  database startup overhead, but a few operating systems (Win32,
Bruce Momjian's avatar
Bruce Momjian committed
1170
  Solaris) might benefit from threading.  Also explore the idea of
1171
  a single session using multiple threads to execute a statement faster.
1172

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1173 1174 1175
* Experiment with multi-threaded backend better resource utilization

  This would allow a single query to make use of multiple CPU's or
Bruce Momjian's avatar
Bruce Momjian committed
1176 1177 1178 1179
  multiple I/O channels simultaneously.  One idea is to create a
  background reader that can pre-fetch sequential and index scan
  pages needed by other backends.  This could be expanded to allow
  concurrent reads from multiple devices in a partitioned table.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1180

Bruce Momjian's avatar
Bruce Momjian committed
1181
* Add connection pooling
1182 1183 1184 1185

  It is unclear if this should be done inside the backend code or done
  by something external like pgpool. The passing of file descriptors to
  existing backends is one of the difficulties with a backend approach.
1186

1187

1188 1189
Write-Ahead Log
===============
1190

1191 1192
* Eliminate need to write full pages to WAL before page modification [wal]

Bruce Momjian's avatar
Bruce Momjian committed
1193
  Currently, to protect against partial disk page writes, we write
1194
  full page images to WAL before they are modified so we can correct any
1195 1196
  partial page writes during recovery.  These pages can also be
  eliminated from point-in-time archive files.
1197

Bruce Momjian's avatar
Bruce Momjian committed
1198 1199
	o  When off, write CRC to WAL and check file system blocks
	   on recovery
Bruce Momjian's avatar
Bruce Momjian committed
1200 1201 1202 1203

	   If CRC check fails during recovery, remember the page in case
	   a later CRC for that page properly matches.

Bruce Momjian's avatar
Bruce Momjian committed
1204 1205 1206 1207
	o  Write full pages during file system write and not when
	   the page is modified in the buffer cache

	   This allows most full page writes to happen in the background
Bruce Momjian's avatar
Bruce Momjian committed
1208 1209 1210
	   writer.  It might cause problems for applying WAL on recovery
	   into a partially-written page, but later the full page will be
	   replaced from WAL.
Bruce Momjian's avatar
Bruce Momjian committed
1211

Bruce Momjian's avatar
Bruce Momjian committed
1212
* Allow WAL traffic to be streamed to another server for stand-by
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1213
  replication
1214
* Reduce WAL traffic so only modified values are written rather than
Bruce Momjian's avatar
Bruce Momjian committed
1215
  entire rows?
1216 1217
* Allow the pg_xlog directory location to be specified during initdb
  with a symlink back to the /data location
Bruce Momjian's avatar
Bruce Momjian committed
1218
* Allow WAL information to recover corrupted pg_controldata
1219

1220
  http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php
1221

Bruce Momjian's avatar
Bruce Momjian committed
1222 1223
* Find a way to reduce rotational delay when repeatedly writing
  last WAL page
Bruce Momjian's avatar
Bruce Momjian committed
1224

1225 1226 1227
  Currently fsync of WAL requires the disk platter to perform a full
  rotation to fsync again. One idea is to write the WAL to different
  offsets that might reduce the rotational delay.
1228

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1229 1230 1231 1232
* Allow buffered WAL writes and fsync

  Instead of guaranteeing recovery of all committed transactions, this
  would provide improved performance by delaying WAL writes and fsync
Bruce Momjian's avatar
Bruce Momjian committed
1233
  so an abrupt operating system restart might lose a few seconds of
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1234 1235 1236 1237
  committed transactions but still be consistent.  We could perhaps
  remove the 'fsync' parameter (which results in an an inconsistent
  database) in favor of this capability.

Bruce Momjian's avatar
Bruce Momjian committed
1238 1239
* Allow WAL logging to be turned off for a table, but the table
  might be dropped or truncated during crash recovery [walcontrol]
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1240 1241

  Allow tables to bypass WAL writes and just fsync() dirty pages on
Bruce Momjian's avatar
Bruce Momjian committed
1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255
  commit.  This should be implemented using ALTER TABLE, e.g. ALTER 
  TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ].  Tables using 
  non-default logging should not use referential integrity with 
  default-logging tables.  A table without dirty buffers during a
  crash could perhaps avoid the drop/truncate.

* Allow WAL logging to be turned off for a table, but the table would
  avoid being truncated/dropped [walcontrol]

  To do this, only a single writer can modify the table, and writes 
  must happen only on new pages so the new pages can be removed during
  crash recovery.  Readers can continue accessing the table.  Such 
  tables probably cannot have indexes.  One complexity is the handling 
  of indexes on TOAST tables.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1256

Bruce Momjian's avatar
Bruce Momjian committed
1257

1258 1259
Optimizer / Executor
====================
1260

Bruce Momjian's avatar
Bruce Momjian committed
1261
* Improve selectivity functions for geometric operators
Bruce Momjian's avatar
Bruce Momjian committed
1262
* Allow ORDER BY ... LIMIT # to select high/low value without sort or
1263 1264
  index using a sequential scan for highest/lowest values

Bruce Momjian's avatar
Bruce Momjian committed
1265
  Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
1266 1267
  all values to return the high/low value.  Instead The idea is to do a 
  sequential scan to find the high/low value, thus avoiding the sort.
Bruce Momjian's avatar
Bruce Momjian committed
1268
  MIN/MAX already does this, but not for LIMIT > 1.
1269

1270
* Precompile SQL functions to avoid overhead
Bruce Momjian's avatar
Bruce Momjian committed
1271
* Create utility to compute accurate random_page_cost value
Bruce Momjian's avatar
Bruce Momjian committed
1272
* Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1273
* Have EXPLAIN ANALYZE highlight poor optimizer estimates
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1274 1275
* Consider using hash buckets to do DISTINCT, rather than sorting

Bruce Momjian's avatar
Bruce Momjian committed
1276 1277
  This would be beneficial when there are few distinct values.  This is
  already used by GROUP BY.
Bruce Momjian's avatar
Bruce Momjian committed
1278

1279
* Log statements where the optimizer row estimates were dramatically
Bruce Momjian's avatar
Bruce Momjian committed
1280
  different from the number of rows actually found?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1281

Bruce Momjian's avatar
Bruce Momjian committed
1282

Bruce Momjian's avatar
Bruce Momjian committed
1283 1284
Miscellaneous Performance
=========================
1285 1286

* Do async I/O for faster random read-ahead of data
1287 1288 1289

  Async I/O allows multiple I/O requests to be sent to the disk with
  results coming back asynchronously.
Bruce Momjian's avatar
Bruce Momjian committed
1290

Bruce Momjian's avatar
Bruce Momjian committed
1291
* Use mmap() rather than SYSV shared memory or to write WAL files?
1292 1293

  This would remove the requirement for SYSV SHM but would introduce
Bruce Momjian's avatar
Bruce Momjian committed
1294 1295
  portability issues. Anonymous mmap (or mmap to /dev/zero) is required
  to prevent I/O overhead.
Bruce Momjian's avatar
Bruce Momjian committed
1296 1297 1298

* Consider mmap()'ing files into a backend?

Bruce Momjian's avatar
Bruce Momjian committed
1299 1300 1301
  Doing I/O to large tables would consume a lot of address space or
  require frequent mapping/unmapping.  Extending the file also causes
  mapping problems that might require mapping only individual pages,
Bruce Momjian's avatar
Bruce Momjian committed
1302
  leading to thousands of mappings.  Another problem is that there is no
Bruce Momjian's avatar
Bruce Momjian committed
1303
  way to _prevent_ I/O to disk from the dirty shared buffers so changes
Bruce Momjian's avatar
Bruce Momjian committed
1304
  could hit disk before WAL is written.
1305

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1306
* Add a script to ask system configuration questions and tune postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
1307 1308 1309 1310 1311 1312 1313 1314 1315
* Merge xmin/xmax/cmin/cmax back into three header fields

  Before subtransactions, there used to be only three fields needed to
  store these four values. This was possible because only the current
  transaction looks at the cmin/cmax values. If the current transaction
  created and expired the row the fields stored where xmin (same as
  xmax), cmin, cmax, and if the transaction was expiring a row from a
  another transaction, the fields stored were xmin (cmin was not
  needed), xmax, and cmax. Such a system worked because a transaction
Bruce Momjian's avatar
Bruce Momjian committed
1316
  could only see rows from another completed transaction. However,
Bruce Momjian's avatar
Bruce Momjian committed
1317 1318 1319 1320 1321
  subtransactions can see rows from outer transactions, and once the
  subtransaction completes, the outer transaction continues, requiring
  the storage of all four fields. With subtransactions, an outer
  transaction can create a row, a subtransaction expire it, and when the
  subtransaction completes, the outer transaction still has to have
Bruce Momjian's avatar
Bruce Momjian committed
1322
  proper visibility of the row's cmin, for example, for cursors.
Bruce Momjian's avatar
Bruce Momjian committed
1323 1324

  One possible solution is to create a phantom cid which represents a
Bruce Momjian's avatar
Bruce Momjian committed
1325 1326
  cmin/cmax pair and is stored in local memory.  Another idea is to
  store both cmin and cmax only in local memory.
Bruce Momjian's avatar
Bruce Momjian committed
1327

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1328
* Research storing disk pages with no alignment/padding
1329

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1330

1331
Source Code
1332 1333
===========

Bruce Momjian's avatar
Bruce Momjian committed
1334
* Add use of 'const' for variables in source tree
Bruce Momjian's avatar
Bruce Momjian committed
1335
* Move some things from /contrib into main tree
Bruce Momjian's avatar
Bruce Momjian committed
1336
* Move some /contrib modules out to their own project sites
1337 1338 1339 1340

  Particularly, move GPL-licensed /contrib/userlock and 
  /contrib/dbmirror/clean_pending.pl.

Bruce Momjian's avatar
Bruce Momjian committed
1341
* %Remove warnings created by -Wcast-align
Bruce Momjian's avatar
Bruce Momjian committed
1342
* Move platform-specific ps status display info from ps_status.c to ports
Bruce Momjian's avatar
Bruce Momjian committed
1343
* Add optional CRC checksum to heap and index pages
Bruce Momjian's avatar
Bruce Momjian committed
1344
* Improve documentation to build only interfaces (Marc)
1345
* Remove or relicense modules that are not under the BSD license, if possible
Bruce Momjian's avatar
Bruce Momjian committed
1346
* %Remove memory/file descriptor freeing before ereport(ERROR)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1347
* Acquire lock on a relation before building a relcache entry for it
Bruce Momjian's avatar
Bruce Momjian committed
1348 1349
* %Promote debug_query_string into a server-side function current_query()
* %Allow the identifier length to be increased via a configure option
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1350
* Allow cross-compiling by generating the zic database on the target system
Neil Conway's avatar
Neil Conway committed
1351
* Improve NLS maintenance of libpgport messages linked onto applications
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1352
* Allow ecpg to work with MSVC and BCC
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1353
* Add xpath_array() to /contrib/xml2 to return results as an array
Bruce Momjian's avatar
Bruce Momjian committed
1354 1355 1356 1357 1358
* Allow building in directories containing spaces

  This is probably not possible because 'gmake' and other compiler tools
  do not fully support quoting of paths with spaces.

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1359
* -Allow installing to directories containing spaces
Bruce Momjian's avatar
Bruce Momjian committed
1360 1361 1362 1363 1364

  This is possible if proper quoting is added to the makefiles for the
  install targets.  Because PostgreSQL supports relocatable installs, it
  is already possible to install into a directory that doesn't contain 
  spaces and then copy the install to a directory with spaces.
Bruce Momjian's avatar
Bruce Momjian committed
1365

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1366
* Fix sgmltools so PDFs can be generated with bookmarks
Neil Conway's avatar
Neil Conway committed
1367
* -%Clean up compiler warnings (especially with gcc version 4)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1368 1369
* Use UTF8 encoding for NLS messages so all server encodings can
  read them properly
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1370
* Update Bonjour to work with newer cross-platform SDK
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1371
* -Remove BeOS and QNX-specific code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1372 1373
* Split out libpq pgpass and environment documentation sections to make
  it easier for non-developers to find
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1374 1375 1376 1377
* Improve port/qsort() to handle sorts with 50% unique and 50% duplicate
  value [qsort]

  This involves choosing better pivot points for the quicksort.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1378

Bruce Momjian's avatar
Bruce Momjian committed
1379 1380
* Consider GnuTLS if OpenSSL license becomes a problem

1381
  http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php
Bruce Momjian's avatar
Bruce Momjian committed
1382

Bruce Momjian's avatar
Bruce Momjian committed
1383

1384
* Win32
1385

1386 1387 1388 1389 1390 1391 1392
	o Remove configure.in check for link failure when cause is found
	o Remove readdir() errno patch when runtime/mingwex/dirent.c rev
	  1.4 is released
	o Remove psql newline patch when we find out why mingw outputs an
	  extra newline
	o Allow psql to use readline once non-US code pages work with
	  backslashes
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1393 1394
	o Re-enable timezone output on log_line_prefix '%t' when a
	  shorter timezone string is available
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1395
	o Fix problem with shared memory on the Win32 Terminal Server
1396 1397
	o Improve signal handling

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1398
	  http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php
1399

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1400 1401 1402 1403
	o Add long file support for binary pg_dump output

	  While Win32 supports 64-bit files, the MinGW API does not,
	  meaning we have to build an fseeko replacement on top of the
Bruce Momjian's avatar
Bruce Momjian committed
1404 1405 1406
	  Win32 API, and we have to make sure MinGW handles it.  Another
	  option is to wait for the MinGW project to fix it, or use the
	  code from the LibGW32C project as a guide.
Bruce Momjian's avatar
Bruce Momjian committed
1407

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1408
	o -Port contrib/xml2
Bruce Momjian's avatar
Bruce Momjian committed
1409
	o Check WSACancelBlockingCall() for interrupts [win32intr]
Bruce Momjian's avatar
Bruce Momjian committed
1410

Bruce Momjian's avatar
Bruce Momjian committed
1411

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1412
* Wire Protocol Changes
1413

1414
	o Allow dynamic character set handling
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1415
	o Add decoded type, length, precision
1416
	o Use compression?
Bruce Momjian's avatar
Bruce Momjian committed
1417
	o Update clients to use data types, typmod, schema.table.column names
1418
	  of result sets using new statement protocol
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1419

1420

1421 1422 1423 1424 1425
---------------------------------------------------------------------------


Developers who have claimed items are:
--------------------------------------
Bruce Momjian's avatar
Bruce Momjian committed
1426
* Alvaro is Alvaro Herrera <alvherre@dcc.uchile.cl>
Bruce Momjian's avatar
Bruce Momjian committed
1427
* Andrew is Andrew Dunstan <andrew@dunslane.net>
Bruce Momjian's avatar
Bruce Momjian committed
1428
* Bruce is Bruce Momjian <bruce@momjian.us> of EnterpriseDB
Bruce Momjian's avatar
Bruce Momjian committed
1429 1430 1431
* Christopher is Christopher Kings-Lynne <chriskl@familyhealth.com.au> of
    Family Health Network
* D'Arcy is D'Arcy J.M. Cain <darcy@druid.net> of The Cain Gang Ltd.
Bruce Momjian's avatar
Bruce Momjian committed
1432
* Fabien is Fabien Coelho <coelho@cri.ensmp.fr>
Bruce Momjian's avatar
Bruce Momjian committed
1433 1434
* Gavin is Gavin Sherry <swm@linuxworld.com.au> of Alcove Systems Engineering
* Greg is Greg Sabino Mullane <greg@turnstep.com>
Bruce Momjian's avatar
Bruce Momjian committed
1435
* Jan is Jan Wieck <JanWieck@Yahoo.com> of Afilias, Inc.
Bruce Momjian's avatar
Bruce Momjian committed
1436
* Joe is Joe Conway <mail@joeconway.com>
1437
* Karel is Karel Zak <zakkr@zf.jcu.cz>
Bruce Momjian's avatar
Fix :  
Bruce Momjian committed
1438
* Magnus is Magnus Hagander <mha@sollentuna.net>
Bruce Momjian's avatar
Bruce Momjian committed
1439
* Marc is Marc Fournier <scrappy@hub.org> of PostgreSQL, Inc.
Bruce Momjian's avatar
Bruce Momjian committed
1440
* Matthew T. O'Connor <matthew@zeut.net>
Bruce Momjian's avatar
Bruce Momjian committed
1441
* Michael is Michael Meskes <meskes@postgresql.org> of Credativ
Bruce Momjian's avatar
Bruce Momjian committed
1442
* Neil is Neil Conway <neilc@samurai.com>
Bruce Momjian's avatar
Bruce Momjian committed
1443
* Oleg is Oleg Bartunov <oleg@sai.msu.su>
1444
* Peter is Peter Eisentraut <peter_e@gmx.net>
Bruce Momjian's avatar
Bruce Momjian committed
1445
* Philip is Philip Warner <pjw@rhyme.com.au> of Albatross Consulting Pty. Ltd.
Bruce Momjian's avatar
Bruce Momjian committed
1446
* Rod is Rod Taylor <pg@rbt.ca>
Bruce Momjian's avatar
Bruce Momjian committed
1447
* Simon is Simon Riggs <simon@2ndquadrant.com>
Bruce Momjian's avatar
Bruce Momjian committed
1448
* Stephan is Stephan Szabo <sszabo@megazone23.bigpanda.com>
Bruce Momjian's avatar
Bruce Momjian committed
1449
* Tatsuo is Tatsuo Ishii <t-ishii@sra.co.jp> of Software Research Assoc.
Bruce Momjian's avatar
Bruce Momjian committed
1450
* Teodor is Teodor Sigaev <teodor@sigaev.ru>
Bruce Momjian's avatar
Bruce Momjian committed
1451
* Tom is Tom Lane <tgl@sss.pgh.pa.us> of Red Hat