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:		Tue Jul 25 20:34:56 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
	  o Allow point-in-time recovery to archive partially filled
Bruce Momjian's avatar
Bruce Momjian committed
148
	    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
Bruce Momjian's avatar
Bruce Momjian committed
160
	    recovery.  A function call to do this would also be useful.
161
	    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
Bruce Momjian committed
171 172
	  o Add reporting of the current WAL file and offset, perhaps as
	    part of partial log file archiving
Bruce Momjian's avatar
Bruce Momjian committed
173

174 175 176
	    The offset allows parts of a WAL file to be archived using
	    an external program.

Bruce Momjian's avatar
Bruce Momjian committed
177 178 179 180 181 182 183 184 185

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
186
* %Add ability to monitor the use of temporary sort files
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
187
* -Allow server logs to be remotely read and removed using SQL commands
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
188
* Allow protocol-level BIND parameter values to be logged
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
189

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

Bruce Momjian's avatar
Bruce Momjian committed
192

193 194
Data Types
==========
195

Bruce Momjian's avatar
Bruce Momjian committed
196 197 198 199
* 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
200
  http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php
Bruce Momjian's avatar
Bruce Momjian committed
201

202
* Change NUMERIC to enforce the maximum precision
Bruce Momjian's avatar
Bruce Momjian committed
203 204 205 206 207 208 209 210 211 212 213
* 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.

214 215 216 217 218
* %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
219 220
* %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump
  does not dump the changes
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
221
* Fix data types where equality comparison isn't intuitive, e.g. box
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
222 223
* -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
224
* -Allow INET + INT8 to increment the host part of the address or
Bruce Momjian's avatar
Bruce Momjian committed
225
  throw an error on overflow
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
226
* -Add 'tid != tid ' operator for use in corruption recovery
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
227 228
* Allow user-defined types to specify a type modifier at table creation
  time
Bruce Momjian's avatar
Bruce Momjian committed
229
* Allow user-defined types to accept 'typmod' parameters
Bruce Momjian's avatar
Bruce Momjian committed
230

Bruce Momjian's avatar
Bruce Momjian committed
231 232
  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
233

Bruce Momjian's avatar
>  
Bruce Momjian committed
234 235 236 237
* Add support for public SYNONYMs

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
238 239 240 241
* Fix CREATE CAST on DOMAINs

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

Bruce Momjian's avatar
Bruce Momjian committed
242
* Add Globally/Universally Unique Identifier (GUID/UUID)
243 244
* Dates and Times

Bruce Momjian's avatar
Bruce Momjian committed
245
	o Allow infinite dates and intervals just like infinite timestamps
246 247
	o Merge hardwired timezone names with the TZ database; allow either 
	  kind everywhere a TZ name is currently taken
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
248
	o -Allow customization of the known set of TZ names (generalize the
249 250 251 252 253
	  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
254
	  computations should adjust based on the time zone rules.
255

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
256
	o -Allow timezone names in SQL strings, '2006-05-24 21:11
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
257
	   Americas/New_York'::timestamptz
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
258
	o Fix SELECT '0.01 years'::interval, '0.01 months'::interval
Bruce Momjian's avatar
Bruce Momjian committed
259 260 261 262 263 264 265 266 267 268 269 270 271
	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	
272
	o Add ISO INTERVAL handling
273 274

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

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
277
		o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO 
278
		  SECOND
279 280 281
		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
282 283 284 285 286
		  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'.
287 288 289

		  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
290 291 292 293 294 295 296 297 298 299
		  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.
300

301 302 303 304 305 306 307 308 309
		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
310

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
311
	o -Allow NULLs in arrays
Bruce Momjian's avatar
Bruce Momjian committed
312 313
	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
314

Bruce Momjian's avatar
Bruce Momjian committed
315

316 317
* Binary Data

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

Bruce Momjian's avatar
Bruce Momjian committed
322
          /contrib/lo offers this functionality.
323 324 325

	o Allow read/write into TOAST values like large objects

326
	  This requires the TOAST column to be stored EXTERNAL.
327

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
328 329 330 331
	o Add API for 64-bit large object access

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

332

Bruce Momjian's avatar
Bruce Momjian committed
333 334 335 336
Functions
=========

* Allow INET subnet tests using non-constants to be indexed
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
337
* -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
Bruce Momjian's avatar
Bruce Momjian committed
338 339 340 341 342 343 344
  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
345
* %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Bruce Momjian's avatar
Bruce Momjian committed
346
  pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
347
* -Allow to_char() to print localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
348
* Allow to_date() and to_timestamp() accept localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
349 350 351 352
* Add missing parameter handling in to_char()

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

Bruce Momjian's avatar
Bruce Momjian committed
353 354 355 356 357 358 359 360 361 362 363 364 365 366 367
* 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
368
* -Add sleep() function, remove from regress.c
Bruce Momjian's avatar
Bruce Momjian committed
369
* -Allow user-defined functions retuning a domain value to enforce domain
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
370
  constraints
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
371
* Add SPI_gettypmod() to return the typemod for a TupleDesc
Bruce Momjian's avatar
Bruce Momjian committed
372

Bruce Momjian's avatar
Bruce Momjian committed
373

374 375
Multi-Language Support
======================
Bruce Momjian's avatar
Bruce Momjian committed
376

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

Bruce Momjian's avatar
Bruce Momjian committed
380 381 382 383
  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.
384 385 386

* Allow encoding on a per-column basis

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

390
* Add CREATE COLLATE?  [locale]
Bruce Momjian's avatar
Bruce Momjian committed
391
* Support multiple simultaneous character sets, per SQL92
Bruce Momjian's avatar
Bruce Momjian committed
392
* Improve UTF8 combined character handling?
393 394
* 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
395
* Fix problems with wrong runtime encoding conversion for NLS message files
Bruce Momjian's avatar
Bruce Momjian committed
396 397 398
* 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
399

Bruce Momjian's avatar
Bruce Momjian committed
400 401 402 403
* Fix ILIKE and regular expressions to handle case insensitivity
  properly in multibyte encodings

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

406

407 408
Views / Rules
=============
Bruce Momjian's avatar
Bruce Momjian committed
409

Neil Conway's avatar
Neil Conway committed
410
* Automatically create rules on views so they are updateable, per SQL99
Bruce Momjian's avatar
Bruce Momjian committed
411 412

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

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

Bruce Momjian's avatar
Bruce Momjian committed
420 421 422 423
  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
424

425 426
SQL Commands
============
Bruce Momjian's avatar
Bruce Momjian committed
427

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

  This is like DELETE CASCADE, but truncates.

Bruce Momjian's avatar
Bruce Momjian committed
436
* %Add a separate TRUNCATE permission
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
437 438 439 440

  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
441
* Allow PREPARE of cursors
Neil Conway's avatar
Neil Conway committed
442 443
* -Allow PREPARE to automatically determine parameter types based on the SQL
  statement (Neil)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
444 445 446 447 448 449 450 451
* 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
452 453
* Invalidate prepared queries, like INSERT, when the table definition
  is altered
454 455 456 457 458
* 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
459
* Add optional textual message to NOTIFY
460 461 462 463 464

  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
465
* Add a GUC variable to warn about non-standard SQL usage in queries
466
* Add SQL-standard MERGE command, typically used to merge two tables
Bruce Momjian's avatar
Bruce Momjian committed
467
  [merge]
468 469 470 471 472 473

  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
474
  [merge]
Bruce Momjian's avatar
Bruce Momjian committed
475 476

  To implement this cleanly requires that the table have a unique index
477 478 479
  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
480

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

  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)'.

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
493
  This would include resetting of all variables (RESET ALL), dropping of
494 495 496 497
  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
498 499
  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 
500
  notify the protocol when a RESET CONNECTION command is used.
Bruce Momjian's avatar
Bruce Momjian committed
501
  http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
502

503
* Add GUC to issue notice about statements that use unjoined tables
504
* Allow EXPLAIN to identify tables that were skipped because of 
505
  constraint_exclusion
506
* Allow EXPLAIN output to be more easily processed by scripts
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
507 508 509 510 511 512 513 514 515
* -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
516
* Simplify dropping roles that have objects in several databases
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
517
* Allow COMMENT ON to accept an expression rather than just a string
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
518 519
* 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
520
* Make CLUSTER preserve recently-dead tuples per MVCC requirements
Bruce Momjian's avatar
Bruce Momjian committed
521
* Add SQL99 WITH clause to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
522
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
523 524 525 526
* 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
527

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
528 529 530
* Add a GUC to control whether BEGIN inside a transcation should abort
  the transaction.

Bruce Momjian's avatar
Bruce Momjian committed
531

532 533 534 535 536 537
* 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
538
	o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT
539 540 541 542


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


Bruce Momjian's avatar
Bruce Momjian committed
549
* ALTER
550

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

555
	  http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php
556

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

563
	  Currently non-global system tables must be in the default database
564
	  tablespace. Global system tables can never be moved.
565

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
566
	o Prevent parent tables from altering or dropping constraints
567 568 569 570
	  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
571
	o -Add ALTER TABLE tab INHERIT / NO INHERIT  parent
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
572
	o Have ALTER INDEX update the name of a constraint using that index
Bruce Momjian's avatar
Bruce Momjian committed
573
	o Add ALTER TABLE RENAME CONSTRAINT, update index name also
Bruce Momjian's avatar
Bruce Momjian committed
574

Bruce Momjian's avatar
Bruce Momjian committed
575

Bruce Momjian's avatar
Bruce Momjian committed
576
* CLUSTER
577

Bruce Momjian's avatar
Bruce Momjian committed
578
	o Automatically maintain clustering on a table
579

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

Bruce Momjian's avatar
Bruce Momjian committed
588
	o %Add default clustering to system tables
Bruce Momjian's avatar
Bruce Momjian committed
589

590 591
	  To do this, determine the ideal cluster index for each system
	  table and set the cluster setting during initdb.
592

Bruce Momjian's avatar
Bruce Momjian committed
593

Bruce Momjian's avatar
Bruce Momjian committed
594
* COPY
595

596
	o Allow COPY to report error lines and continue
597

598 599
	  This requires the use of a savepoint before each COPY line is
	  processed, with ROLLBACK on COPY failure.
600

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

Bruce Momjian's avatar
Bruce Momjian committed
604
	  On crash recovery, the table involved in the COPY would
Bruce Momjian's avatar
Bruce Momjian committed
605
	  be removed or have its heap and index files truncated.  One
Bruce Momjian's avatar
Bruce Momjian committed
606 607 608
	  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
609

Bruce Momjian's avatar
Bruce Momjian committed
610
	o Allow COPY to output from SELECT
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
611

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
615

Bruce Momjian's avatar
Bruce Momjian committed
616
* GRANT/REVOKE
617

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

	  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
626
	o Allow GRANT/REVOKE permissions to be inherited by objects based on
Bruce Momjian's avatar
Bruce Momjian committed
627 628
	  schema permissions

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

Bruce Momjian's avatar
Bruce Momjian committed
631

Bruce Momjian's avatar
Bruce Momjian committed
632
* CURSOR
633

634
	o Allow UPDATE/DELETE WHERE CURRENT OF cursor
635

636 637 638 639
	  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.
640 641

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

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

646 647
	  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
648

Bruce Momjian's avatar
Bruce Momjian committed
649

Bruce Momjian's avatar
Bruce Momjian committed
650
* INSERT
651

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

656 657
	  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
658 659
	  the insert.  
	  http://archives.postgresql.org/pgsql-patches/2005-07/msg00568.php
Bruce Momjian's avatar
Bruce Momjian committed
660

Bruce Momjian's avatar
Bruce Momjian committed
661

Bruce Momjian's avatar
Bruce Momjian committed
662
* SHOW/SET
663

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

668
	  This is basically the same as SET search_path.
Bruce Momjian's avatar
Bruce Momjian committed
669

Bruce Momjian's avatar
Bruce Momjian committed
670

Bruce Momjian's avatar
Bruce Momjian committed
671 672 673 674 675 676
* 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
677 678 679 680 681
	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
682 683


684 685
* Server-Side Languages

686 687 688
	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
689
		  get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
690 691 692 693 694 695 696 697 698 699 700 701
		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
702 703 704 705 706
		o Add support for WITH HOLD and SCROLL cursors

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

707 708 709 710
		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
711 712 713 714
		o Fix memory leak from exceptions

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
715 716 717 718
		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
719 720 721 722 723 724 725 726

	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
727 728 729
		o Add PL/Python tracebacks

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
731 732 733 734
		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
735

736 737
Clients
=======
738

739
* -Have initdb set the input DateStyle (MDY or DMY) based on locale
740 741 742
* 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
743

744 745 746 747
  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.
748

749 750

* psql
Bruce Momjian's avatar
Bruce Momjian committed
751

752 753 754 755 756 757 758
	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
759
	o Fix psql's \d commands more consistent
Bruce Momjian's avatar
Bruce Momjian committed
760 761

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

764 765 766
	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
767
	o -Improve psql's handling of multi-line statements
Bruce Momjian's avatar
Bruce Momjian committed
768

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

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

	  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
Done:  
Bruce Momjian committed
779
	o -Display IN, INOUT, and OUT parameters in \df
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
780 781 782 783 784
	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
785 786 787 788 789 790 791 792 793
	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
794

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

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

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

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

Bruce Momjian's avatar
Bruce Momjian committed
818

819 820
* ecpg

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

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

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

Bruce Momjian's avatar
Bruce Momjian committed
838

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

	o Add a function to support Parse/DescribeStatement capability
Bruce Momjian's avatar
Bruce Momjian committed
842
	o Add PQescapeIdentifierConn()
843 844 845 846 847
	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

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

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


Bruce Momjian's avatar
Bruce Momjian committed
859 860
Triggers
========
861 862 863 864 865 866
* 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
867
* Allow DEFERRABLE UNIQUE constraints?
868
* Allow triggers to be disabled in only the current session.
869

870 871 872
  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
873
  TRIGGER requires a table lock so it is not ideal for this usage.
874

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

  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
880
* Allow statement-level triggers to access modified rows
Bruce Momjian's avatar
Bruce Momjian committed
881 882
* Support triggers on columns

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

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

887 888 889 890 891
  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
892

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

Bruce Momjian's avatar
Bruce Momjian committed
896 897 898
* 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
899 900 901 902

  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
903
* Track dependencies in function bodies and recompile/invalidate
904

Bruce Momjian's avatar
Bruce Momjian committed
905 906
  This is particularly important for references to temporary tables
  in PL/PgSQL because PL/PgSQL caches query plans.  The only workaround
907 908 909
  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
910

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
911

912 913
Exotic Features
===============
914

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

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

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

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

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

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

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

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

Bruce Momjian's avatar
Bruce Momjian committed
941 942 943 944 945 946 947 948 949 950 951 952
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
953
* Allow SELECT ... FOR UPDATE on inherited tables
Bruce Momjian's avatar
Bruce Momjian committed
954 955 956 957 958 959 960 961 962 963 964 965
* 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
966
  http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
Bruce Momjian's avatar
Bruce Momjian committed
967 968 969 970 971 972 973

* 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
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
974
* -Add fillfactor to control reserved free space during index creation
Bruce Momjian's avatar
Bruce Momjian committed
975 976 977 978 979 980 981 982
* 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.

983
* Allow constraint_exclusion to work for UNIONs like it does for
984 985
  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
986 987
* Allow CREATE INDEX to take an additional parameter for use with
  special index types
Bruce Momjian's avatar
Bruce Momjian committed
988
* Consider compressing indexes by storing key values duplicated in
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
989
  several rows as a single index entry
Bruce Momjian's avatar
Bruce Momjian committed
990

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

Bruce Momjian's avatar
Bruce Momjian committed
993

994 995 996 997 998
* 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
999 1000

* Hash
1001

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

Bruce Momjian's avatar
Bruce Momjian committed
1004
	  Currently only one hash bucket can be stored on a page. Ideally
Bruce Momjian's avatar
Bruce Momjian committed
1005 1006 1007 1008 1009 1010 1011 1012
	  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
1013

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

1017

1018 1019
Fsync
=====
1020

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

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

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

1031

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1038
  Posix_fadvise() can control both sequential/random file caching and
Bruce Momjian's avatar
Bruce Momjian committed
1039 1040 1041 1042
  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.

1043 1044 1045 1046
* 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
1047 1048 1049 1050 1051
  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
1052 1053
* Add estimated_count(*) to return an estimate of COUNT(*)

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

1057 1058
* Allow data to be pulled directly from indexes

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

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

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

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

1082 1083 1084 1085
  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
1086

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1087 1088 1089 1090
* 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
1091

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

1095 1096
* Improve speed with indexes

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

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

  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
1107 1108
* Auto-fill the free space map by scanning the buffer cache or by
  checking pages written by the background writer
1109 1110

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1113 1114 1115 1116 1117 1118
* 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
1119 1120 1121 1122
  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
1123

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1124
* -Add system view to show free space map contents
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1125 1126
* 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
1127 1128
* Allow FSM page return free space based on table clustering, to assist
  in maintaining clustering?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1129
* Consider shrinking expired tuples to just their headers
Bruce Momjian's avatar
Bruce Momjian committed
1130

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1136 1137 1138 1139
  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.
1140
  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
Bruce Momjian's avatar
Bruce Momjian committed
1141
  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php
1142

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1154

1155 1156
Locking
=======
1157

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

1160

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

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

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1172 1173 1174
* 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
1175 1176 1177 1178
  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
1179

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

  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.
1185

1186

1187 1188
Write-Ahead Log
===============
1189

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

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

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

	   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
1203 1204 1205 1206
	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
1207 1208 1209
	   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
1210

Bruce Momjian's avatar
Bruce Momjian committed
1211
* Allow WAL traffic to be streamed to another server for stand-by
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1212
  replication
1213
* Reduce WAL traffic so only modified values are written rather than
Bruce Momjian's avatar
Bruce Momjian committed
1214
  entire rows?
1215 1216
* 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
1217
* Allow WAL information to recover corrupted pg_controldata
1218

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

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

1224 1225 1226
  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.
1227

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1228 1229 1230 1231
* 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
1232
  so an abrupt operating system restart might lose a few seconds of
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1233 1234 1235 1236
  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
1237 1238
* 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
1239 1240

  Allow tables to bypass WAL writes and just fsync() dirty pages on
Bruce Momjian's avatar
Bruce Momjian committed
1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254
  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
1255

Bruce Momjian's avatar
Bruce Momjian committed
1256

1257 1258
Optimizer / Executor
====================
1259

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

Bruce Momjian's avatar
Bruce Momjian committed
1264
  Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
1265 1266
  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
1267
  MIN/MAX already does this, but not for LIMIT > 1.
1268

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

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1281

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

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

  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
1289

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

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1298 1299 1300
  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
1301
  leading to thousands of mappings.  Another problem is that there is no
Bruce Momjian's avatar
Bruce Momjian committed
1302
  way to _prevent_ I/O to disk from the dirty shared buffers so changes
Bruce Momjian's avatar
Bruce Momjian committed
1303
  could hit disk before WAL is written.
1304

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1305
* Add a script to ask system configuration questions and tune postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
1306 1307 1308 1309 1310 1311 1312 1313 1314
* 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
1315
  could only see rows from another completed transaction. However,
Bruce Momjian's avatar
Bruce Momjian committed
1316 1317 1318 1319 1320
  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
1321
  proper visibility of the row's cmin, for example, for cursors.
Bruce Momjian's avatar
Bruce Momjian committed
1322 1323

  One possible solution is to create a phantom cid which represents a
Bruce Momjian's avatar
Bruce Momjian committed
1324 1325
  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
1326

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1329

1330
Source Code
1331 1332
===========

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

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

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

  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
1364

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1365
* Fix sgmltools so PDFs can be generated with bookmarks
Neil Conway's avatar
Neil Conway committed
1366
* -%Clean up compiler warnings (especially with gcc version 4)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1367 1368
* Use UTF8 encoding for NLS messages so all server encodings can
  read them properly
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1369
* Update Bonjour to work with newer cross-platform SDK
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1370
* -Remove BeOS and QNX-specific code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1371 1372
* 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
1373 1374 1375 1376
* 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
1377

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1382

1383
* Win32
1384

1385 1386 1387 1388 1389 1390 1391
	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
1392 1393
	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
1394
	o Fix problem with shared memory on the Win32 Terminal Server
1395 1396
	o Improve signal handling

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1399 1400 1401 1402
	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
1403 1404 1405
	  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
1406

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

Bruce Momjian's avatar
Bruce Momjian committed
1410

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

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

1419

1420 1421 1422 1423 1424
---------------------------------------------------------------------------


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