TODO 57.1 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)
5
Last updated:		Mon Sep 18 12:23:58 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
  http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php
45

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

Bruce Momjian's avatar
Bruce Momjian committed
48 49
  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
50

Bruce Momjian's avatar
Bruce Momjian committed
51 52 53
* 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
54
* Add function to report the time of the most recent server reload
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
55 56 57
* 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
58 59 60 61
* 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.
62 63
  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
64

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
65
* -Re-enable the GUC full_page_writes in 8.2 when reliability issues have
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
66
  been addressed
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
67 68 69 70 71 72 73 74
* Simplify ability to create partitioned tables

  This would allow creation of partitioned tables without requiring
  creation of rules for INSERT/UPDATE/DELETE, and constraints for
  rapid partition selection.  Options could include range and hash
  partition selection.

* Allow auto-selection of partitioned tables for min/max() operations
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
75

Bruce Momjian's avatar
Bruce Momjian committed
76

Bruce Momjian's avatar
Bruce Momjian committed
77
* Improve replication solutions
78

Bruce Momjian's avatar
Bruce Momjian committed
79
	o Load balancing
Bruce Momjian's avatar
Bruce Momjian committed
80

Bruce Momjian's avatar
Bruce Momjian committed
81 82 83
	  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
84

Bruce Momjian's avatar
Bruce Momjian committed
85
	o Allow replication over unreliable or non-persistent links
86 87


Bruce Momjian's avatar
Bruce Momjian committed
88
* Configuration files
89

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
90
	o -Add "include file" functionality in postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
91
	o Allow commenting of variables in postgresql.conf to restore them
Bruce Momjian's avatar
Bruce Momjian committed
92
	  to defaults
Bruce Momjian's avatar
Bruce Momjian committed
93

Bruce Momjian's avatar
Bruce Momjian committed
94 95
	  Currently, if a variable is commented out, it keeps the
	  previous uncommented value until a server restarted.
96
	  http://archives.postgresql.org/pgsql-hackers/2006-09/msg01481.php
Bruce Momjian's avatar
Bruce Momjian committed
97

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

100 101
	  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
102

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
103 104 105 106 107 108 109 110 111
	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
112
	o %Allow postgresql.conf file values to be changed via an SQL
Bruce Momjian's avatar
Bruce Momjian committed
113
	  API, perhaps using SET GLOBAL
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
114
	o Allow the server to be stopped/restarted via an SQL API
115
	o -Issue a warning if a change-on-restart-only postgresql.conf value
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
116 117
	  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
118

119

Bruce Momjian's avatar
Bruce Momjian committed
120
* Tablespaces
121

Bruce Momjian's avatar
Bruce Momjian committed
122
	o Allow a database in tablespace t1 with tables created in
Bruce Momjian's avatar
Bruce Momjian committed
123 124
	  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
125

Bruce Momjian's avatar
Bruce Momjian committed
126 127 128 129 130 131 132 133
	  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.
134

Bruce Momjian's avatar
Bruce Momjian committed
135
	o Allow reporting of which objects are in which tablespaces
136

Bruce Momjian's avatar
Bruce Momjian committed
137 138 139 140 141
	  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
142

Bruce Momjian's avatar
Bruce Momjian committed
143
	o %Add a GUC variable to control the tablespace for temporary objects
Bruce Momjian's avatar
Bruce Momjian committed
144
	  and sort files
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
145

Bruce Momjian's avatar
Bruce Momjian committed
146 147
	  It could start with a random tablespace from a supplied list and
	  cycle through the list.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
148

Bruce Momjian's avatar
Bruce Momjian committed
149 150
	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
151

Bruce Momjian's avatar
Bruce Momjian committed
152
	o Allow per-tablespace quotas
153 154


155 156
* Point-In-Time Recovery (PITR)

Bruce Momjian's avatar
Bruce Momjian committed
157
	  o Add command to archive partially filled write-ahead logs? [pitr]
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
158

Bruce Momjian's avatar
Bruce Momjian committed
159 160
	    Currently only full WAL files are archived. This means that the
	    most recent transactions aren't available for recovery in case
Bruce Momjian's avatar
Bruce Momjian committed
161
	    of a disk failure.
Bruce Momjian's avatar
Bruce Momjian committed
162

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
163
	  o -Automatically force archiving of partially-filled WAL files when
Bruce Momjian's avatar
Bruce Momjian committed
164
	    pg_stop_backup() is called or the server is stopped
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
165
	  o -Add reporting of the current WAL file and offset, perhaps as
Bruce Momjian's avatar
Bruce Momjian committed
166
	    part of partial log file archiving
Bruce Momjian's avatar
Bruce Momjian committed
167
	  o %Create dump tool for write-ahead logs for use in determining
Bruce Momjian's avatar
Bruce Momjian committed
168
	    transaction id for point-in-time recovery
169
	  o Allow a warm standby system to also allow read-only statements
Bruce Momjian's avatar
Bruce Momjian committed
170 171 172 173 174
	    [pitr]

	    This is useful for checking PITR recovery.

	  o Allow the PITR process to be debugged and data examined
175

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

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

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.

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
211
* Fix data types where equality comparison isn't intuitive, e.g. box
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
212 213
* -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
214
* -Allow INET + INT8 to increment the host part of the address or
Bruce Momjian's avatar
Bruce Momjian committed
215
  throw an error on overflow
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
216
* -Add 'tid != tid ' operator for use in corruption recovery
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
217 218
* Allow user-defined types to specify a type modifier at table creation
  time
Bruce Momjian's avatar
Bruce Momjian committed
219
* Allow user-defined types to accept 'typmod' parameters
Bruce Momjian's avatar
Bruce Momjian committed
220

Bruce Momjian's avatar
Bruce Momjian committed
221 222
  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
223
  http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php
Bruce Momjian's avatar
Bruce Momjian committed
224

Bruce Momjian's avatar
>  
Bruce Momjian committed
225 226 227 228
* Add support for public SYNONYMs

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
229 230 231 232
* Fix CREATE CAST on DOMAINs

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

Bruce Momjian's avatar
Bruce Momjian committed
233
* Add Globally/Universally Unique Identifier (GUID/UUID)
Bruce Momjian's avatar
Bruce Momjian committed
234 235 236

  http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
237 238 239 240
* Add support for SQL-standard GENERATED/IDENTITY columns

  http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
241 242 243
* Support a data type with specific enumerated values (ENUM)

  http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
244

Bruce Momjian's avatar
Bruce Momjian committed
245 246 247 248
* Improve XML support

  http://developer.postgresql.org/index.php/XML_Support

249 250
* Dates and Times

Bruce Momjian's avatar
Bruce Momjian committed
251
	o Allow infinite dates and intervals just like infinite timestamps
252 253
	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
254
	o -Allow customization of the known set of TZ names (generalize the
255 256 257 258 259
	  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
260
	  computations should adjust based on the time zone rules.
261

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

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

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
283
		o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO 
284
		  SECOND
285 286 287
		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
288 289 290 291 292
		  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'.
293 294 295

		  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
296 297 298 299 300 301 302 303 304 305
		  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.
306

307 308 309 310 311 312 313 314 315
		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
316

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
317
	o -Allow NULLs in arrays
Bruce Momjian's avatar
Bruce Momjian committed
318 319
	o Delay resolution of array expression's data type so assignment
	  coercion can be performed on empty array expressions
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
320 321
	o Add support for arrays of domains
	o Add support for arrays of complex types
Bruce Momjian's avatar
Bruce Momjian committed
322

Bruce Momjian's avatar
Bruce Momjian committed
323

324 325
* Binary Data

Bruce Momjian's avatar
Bruce Momjian committed
326
	o Improve vacuum of large objects, like /contrib/vacuumlo?
Bruce Momjian's avatar
Bruce Momjian committed
327
	o Add security checking for large objects
Bruce Momjian's avatar
Bruce Momjian committed
328
	o Auto-delete large objects when referencing row is deleted
329

Bruce Momjian's avatar
Bruce Momjian committed
330
          /contrib/lo offers this functionality.
331 332 333

	o Allow read/write into TOAST values like large objects

334
	  This requires the TOAST column to be stored EXTERNAL.
335

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
336 337 338 339
	o Add API for 64-bit large object access

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

340

Bruce Momjian's avatar
Bruce Momjian committed
341 342 343 344
Functions
=========

* Allow INET subnet tests using non-constants to be indexed
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
345
* -Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
Bruce Momjian's avatar
Bruce Momjian committed
346 347 348 349 350 351 352
  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
353
* %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Bruce Momjian's avatar
Bruce Momjian committed
354
  pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
355 356 357

  These would be for application use, not for use by pg_dump.

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
358
* -Allow to_char() to print localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
359
* Allow to_date() and to_timestamp() accept localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
360 361 362 363
* Add missing parameter handling in to_char()

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

Bruce Momjian's avatar
Bruce Momjian committed
364 365 366 367 368 369 370 371 372 373 374 375 376 377 378
* 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
379
* -Add sleep() function, remove from regress.c
Bruce Momjian's avatar
Bruce Momjian committed
380
* -Allow user-defined functions retuning a domain value to enforce domain
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
381
  constraints
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
382
* Add SPI_gettypmod() to return the typemod for a TupleDesc
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
383
* Allow inlining of set-returning functions
Bruce Momjian's avatar
Bruce Momjian committed
384

Bruce Momjian's avatar
Bruce Momjian committed
385

386 387
Multi-Language Support
======================
Bruce Momjian's avatar
Bruce Momjian committed
388

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

Bruce Momjian's avatar
Bruce Momjian committed
392 393 394 395
  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.
396

Bruce Momjian's avatar
Bruce Momjian committed
397
* Allow encoding on a per-column basis optionally using the ICU library:
398

399
  Right now only one encoding is allowed per database.  [locale]
400
  http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php
Bruce Momjian's avatar
Bruce Momjian committed
401 402
  http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php
  http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php
Bruce Momjian's avatar
Bruce Momjian committed
403
  http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php
404

405
* Add CREATE COLLATE?  [locale]
Bruce Momjian's avatar
Bruce Momjian committed
406
* Support multiple simultaneous character sets, per SQL92
Bruce Momjian's avatar
Bruce Momjian committed
407
* Improve UTF8 combined character handling?
408 409
* 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
410
* Fix problems with wrong runtime encoding conversion for NLS message files
Bruce Momjian's avatar
Bruce Momjian committed
411 412 413
* 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
414

Bruce Momjian's avatar
Bruce Momjian committed
415 416 417 418
* Fix ILIKE and regular expressions to handle case insensitivity
  properly in multibyte encodings

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

Bruce Momjian's avatar
Bruce Momjian committed
421 422 423 424 425
* Set client encoding based on the client operating system encoding

  Currently client_encoding is set in postgresql.conf, which
  defaults to the server encoding.

426

427 428
Views / Rules
=============
Bruce Momjian's avatar
Bruce Momjian committed
429

Neil Conway's avatar
Neil Conway committed
430
* Automatically create rules on views so they are updateable, per SQL99
Bruce Momjian's avatar
Bruce Momjian committed
431 432

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

Bruce Momjian's avatar
Bruce Momjian committed
436
* Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
Bruce Momjian's avatar
Bruce Momjian committed
437
* Allow NOTIFY in rules involving conditionals
Bruce Momjian's avatar
Bruce Momjian committed
438
* Allow VIEW/RULE recompilation when the underlying tables change
439

Bruce Momjian's avatar
Bruce Momjian committed
440 441 442 443
  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
444

445 446
SQL Commands
============
Bruce Momjian's avatar
Bruce Momjian committed
447

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
448
* Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
449
* Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
Bruce Momjian's avatar
Bruce Momjian committed
450
* %Allow SET CONSTRAINTS to be qualified by schema/table name
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
451
* -Allow TRUNCATE ... CASCADE/RESTRICT
Bruce Momjian's avatar
Bruce Momjian committed
452 453 454

  This is like DELETE CASCADE, but truncates.

Bruce Momjian's avatar
Bruce Momjian committed
455
* %Add a separate TRUNCATE permission
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
456 457 458 459

  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
460
* Allow PREPARE of cursors
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
461 462 463 464 465 466 467 468
* 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
469 470
* Invalidate prepared queries, like INSERT, when the table definition
  is altered
471 472 473 474 475
* 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
476
* Add optional textual message to NOTIFY
477 478 479 480 481

  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
482
* Add a GUC variable to warn about non-standard SQL usage in queries
483
* Add SQL-standard MERGE command, typically used to merge two tables
Bruce Momjian's avatar
Bruce Momjian committed
484
  [merge]
485 486 487 488 489 490

  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
491
  [merge]
Bruce Momjian's avatar
Bruce Momjian committed
492 493

  To implement this cleanly requires that the table have a unique index
494 495 496
  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
497

Bruce Momjian's avatar
Bruce Momjian committed
498 499
* Add NOVICE output level for helpful messages like automatic sequence/index
  creation
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
500
* -Add COMMENT ON for all cluster global objects (roles, databases
Bruce Momjian's avatar
Bruce Momjian committed
501
  and tablespaces)
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
502
* -Make row-wise comparisons work per SQL spec
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
503 504 505 506 507

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

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
510
  This would include resetting of all variables (RESET ALL), dropping of
511 512 513 514
  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
515 516
  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 
517
  notify the protocol when a RESET CONNECTION command is used.
Bruce Momjian's avatar
Bruce Momjian committed
518
  http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
519

520
* Add GUC to issue notice about statements that use unjoined tables
521
* Allow EXPLAIN to identify tables that were skipped because of 
522
  constraint_exclusion
523
* Allow EXPLAIN output to be more easily processed by scripts
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
524 525 526 527 528 529 530 531 532
* -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
533
* Simplify dropping roles that have objects in several databases
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
534
* Allow COMMENT ON to accept an expression rather than just a string
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
535 536
* 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
537
* Make CLUSTER preserve recently-dead tuples per MVCC requirements
Bruce Momjian's avatar
Bruce Momjian committed
538
* Add SQL99 WITH clause to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
539
* Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
540 541 542 543
* 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
544

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
545 546
* Add a GUC to control whether BEGIN inside a transcation should abort
  the transaction.
Bruce Momjian's avatar
Bruce Momjian committed
547
* Allow DISTINCT to work in multiple-argument aggregate calls
Bruce Momjian's avatar
Bruce Momjian committed
548 549
* Add column to pg_stat_activity that shows the progress of long-running
  commands like CREATE INDEX and VACUUM
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
550
* Implement SQL:2003 window functions
Bruce Momjian's avatar
Bruce Momjian committed
551

Bruce Momjian's avatar
Bruce Momjian committed
552

553 554 555 556 557 558
* 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
559
	o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT
560 561 562


* UPDATE
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
563 564
	o -Allow an alias to be provided for the target table in
	  UPDATE/DELETE (Neil)
Bruce Momjian's avatar
Bruce Momjian committed
565 566 567
	o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating
	  multiple columns
	o Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
568

569
	  http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php
570

571

Bruce Momjian's avatar
Bruce Momjian committed
572
* ALTER
573

Bruce Momjian's avatar
Bruce Momjian committed
574
	o %Have ALTER TABLE RENAME rename SERIAL sequence names
Bruce Momjian's avatar
Bruce Momjian committed
575
	o Add ALTER DOMAIN to modify the underlying data type
Bruce Momjian's avatar
Bruce Momjian committed
576
	o %Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
577

578
	  http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php
579

Bruce Momjian's avatar
Bruce Momjian committed
580
	o %Allow ALTER TABLE to change constraint deferrability and actions
Bruce Momjian's avatar
Bruce Momjian committed
581
	o Add missing object types for ALTER ... SET SCHEMA
582
	o Allow ALTER TABLESPACE to move to different directories
583
	o Allow databases to be moved to different tablespaces
584 585
	o Allow moving system tables to other tablespaces, where possible

586
	  Currently non-global system tables must be in the default database
587
	  tablespace. Global system tables can never be moved.
588

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
589
	o Prevent parent tables from altering or dropping constraints
590 591 592 593
	  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
594
	o -Add ALTER TABLE tab INHERIT / NO INHERIT  parent
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
595
	o Have ALTER INDEX update the name of a constraint using that index
Bruce Momjian's avatar
Bruce Momjian committed
596
	o Add ALTER TABLE RENAME CONSTRAINT, update index name also
Bruce Momjian's avatar
Bruce Momjian committed
597

Bruce Momjian's avatar
Bruce Momjian committed
598

Bruce Momjian's avatar
Bruce Momjian committed
599
* CLUSTER
600

Bruce Momjian's avatar
Bruce Momjian committed
601
	o Automatically maintain clustering on a table
602

603 604
	  This might require some background daemon to maintain clustering
	  during periods of low usage. It might also require tables to be only
605
	  partially filled for easier reorganization.  Another idea would
606
          be to create a merged heap/index data file so an index lookup would
Bruce Momjian's avatar
Bruce Momjian committed
607
	  automatically access the heap data too.  A third idea would be to
Bruce Momjian's avatar
Bruce Momjian committed
608 609
	  store heap rows in hashed groups, perhaps using a user-supplied
	  hash function.
Bruce Momjian's avatar
Bruce Momjian committed
610
	  http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php
611

Bruce Momjian's avatar
Bruce Momjian committed
612
	o %Add default clustering to system tables
Bruce Momjian's avatar
Bruce Momjian committed
613

614 615
	  To do this, determine the ideal cluster index for each system
	  table and set the cluster setting during initdb.
616

Bruce Momjian's avatar
Bruce Momjian committed
617

Bruce Momjian's avatar
Bruce Momjian committed
618
* COPY
619

620
	o Allow COPY to report error lines and continue
621

622 623
	  This requires the use of a savepoint before each COPY line is
	  processed, with ROLLBACK on COPY failure.
624

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

Bruce Momjian's avatar
Bruce Momjian committed
628
	  On crash recovery, the table involved in the COPY would
Bruce Momjian's avatar
Bruce Momjian committed
629
	  be removed or have its heap and index files truncated.  One
Bruce Momjian's avatar
Bruce Momjian committed
630 631 632
	  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
633

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
634
	o -Allow COPY (SELECT ...) TO 'filename'
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
635

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
636

Bruce Momjian's avatar
Bruce Momjian committed
637
* GRANT/REVOKE
638

Bruce Momjian's avatar
Bruce Momjian committed
639
	o Allow column-level privileges
Bruce Momjian's avatar
Bruce Momjian committed
640
	o %Allow GRANT/REVOKE permissions to be applied to all schema objects
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
641
	  with one command
Bruce Momjian's avatar
Bruce Momjian committed
642 643 644 645 646

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

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

Bruce Momjian's avatar
Bruce Momjian committed
652

Bruce Momjian's avatar
Bruce Momjian committed
653
* CURSOR
654

655
	o Allow UPDATE/DELETE WHERE CURRENT OF cursor
656

657 658 659 660
	  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.
661 662

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

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

667 668
	  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
669

Bruce Momjian's avatar
Bruce Momjian committed
670

Bruce Momjian's avatar
Bruce Momjian committed
671
* INSERT
672

673
	o Allow INSERT/UPDATE of the system-generated oid value for a row
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
674
	o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
675
	o -Allow INSERT/UPDATE ... RETURNING new.col or old.col
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
676 677
	o In rules, allow VALUES() to contain a mixture of 'old' and 'new'
	  references
Bruce Momjian's avatar
Bruce Momjian committed
678

Bruce Momjian's avatar
Bruce Momjian committed
679

Bruce Momjian's avatar
Bruce Momjian committed
680
* SHOW/SET
681

Bruce Momjian's avatar
Bruce Momjian committed
682
	o Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
Bruce Momjian's avatar
Bruce Momjian committed
683
	  ANALYZE, and CLUSTER
Bruce Momjian's avatar
Bruce Momjian committed
684
	o Add SET PATH for schemas?
685

686
	  This is basically the same as SET search_path.
Bruce Momjian's avatar
Bruce Momjian committed
687

Bruce Momjian's avatar
Bruce Momjian committed
688

Bruce Momjian's avatar
Bruce Momjian committed
689 690 691 692 693 694
* 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
695 696 697 698 699
	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
700

701 702 703 704 705 706
	o Allow DEFERRABLE and end-of-statement UNIQUE constraints?

	  This would allow UPDATE tab SET col = col + 1 to work if col has
	  a unique index.  Currently, uniqueness checks are done while the
	  command is being executed, rather than at the end of the statement
	  or transaction.
Bruce Momjian's avatar
Bruce Momjian committed
707
	  http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html
708
	  http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php
709

Bruce Momjian's avatar
Bruce Momjian committed
710

711 712
* Server-Side Languages

713 714 715
	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
716
		  get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
Bruce Momjian's avatar
Bruce Momjian committed
717
		o Add Oracle-style packages  (Pavel)
Bruce Momjian's avatar
Bruce Momjian committed
718

Bruce Momjian's avatar
Bruce Momjian committed
719
		  A package would be a schema with session-local variables,
Bruce Momjian's avatar
Bruce Momjian committed
720
		  public/private functions, and initialization functions.  It
Bruce Momjian's avatar
Bruce Momjian committed
721 722 723
		  is also possible to implement these capabilities
		  in all schemas and not use a separate "packages"
		  syntax at all.
Bruce Momjian's avatar
Bruce Momjian committed
724
		  http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php
Bruce Momjian's avatar
Bruce Momjian committed
725

726 727 728 729 730 731 732 733 734 735 736
		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
737 738 739 740 741
		o Add support for WITH HOLD and SCROLL cursors

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

742 743 744 745
		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
746 747 748 749
		o Fix memory leak from exceptions

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
750 751 752 753
		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
754 755 756 757 758 759 760 761

	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
762 763 764
		o Add PL/Python tracebacks

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

Bruce Momjian's avatar
Bruce Momjian committed
766
		o -Allow PL/python to return composite types and result sets
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
767

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
768

769 770
Clients
=======
771

772
* -Have initdb set the input DateStyle (MDY or DMY) based on locale
773 774 775
* 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
776

777 778 779 780
  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.
781

782 783

* psql
Bruce Momjian's avatar
Bruce Momjian committed
784

785 786 787 788 789 790 791
	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
792
	o Fix psql's \d commands more consistent
Bruce Momjian's avatar
Bruce Momjian committed
793 794

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

797 798 799
	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
800
	o -Improve psql's handling of multi-line statements
Bruce Momjian's avatar
Bruce Momjian committed
801

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

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
806
	o -Allow multi-line column values to align in the proper columns
Bruce Momjian's avatar
Bruce Momjian committed
807 808 809 810 811

	  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
812
	o -Display IN, INOUT, and OUT parameters in \df
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
813 814 815 816 817
	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
818 819 820 821 822 823 824 825 826
	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
827

Bruce Momjian's avatar
Bruce Momjian committed
828
* pg_dump
829

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
830 831
	o -Allow pg_dump to use multiple -t and -n switches, exclusion
	   ability, and regular expression object matching
Bruce Momjian's avatar
Bruce Momjian committed
832
	o %Add dumping of comments on index columns and composite type columns
Bruce Momjian's avatar
Bruce Momjian committed
833
	o %Add full object name to the tag field.  eg. for operators we need
Bruce Momjian's avatar
Bruce Momjian committed
834
	  '=(integer, integer)', instead of just '='.
Bruce Momjian's avatar
Bruce Momjian committed
835
	o Add pg_dumpall custom format dumps?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
836
	o -Update pg_dump and psql to use the new COPY libpq API (Christopher)
Bruce Momjian's avatar
Bruce Momjian committed
837 838
	o Remove unnecessary function pointer abstractions in pg_dump source
	  code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
839 840 841 842
	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
843
	o Add options like pg_restore -l and -L to pg_dump
Bruce Momjian's avatar
Bruce Momjian committed
844
	o Stop dumping CASCADE on DROP TYPE commands in clean mode
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
845 846
	o Allow pg_dump --clean to drop roles that own objects or have
	  privileges
Bruce Momjian's avatar
Bruce Momjian committed
847
	o Add -f to pg_dumpall
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
848

Bruce Momjian's avatar
Bruce Momjian committed
849

850 851
* ecpg

Michael Meskes's avatar
Michael Meskes committed
852
	o Docs
853

854 855
	  Document differences between ecpg and the SQL standard and
	  information about the Informix-compatibility module.
856

Bruce Momjian's avatar
Bruce Momjian committed
857
	o Solve cardinality > 1 for input descriptors / variables?
Bruce Momjian's avatar
Bruce Momjian committed
858
	o Add a semantic check level, e.g. check if a table really exists
Bruce Momjian's avatar
Bruce Momjian committed
859
	o fix handling of DB attributes that are arrays
Bruce Momjian's avatar
Bruce Momjian committed
860
	o Use backend PREPARE/EXECUTE facility for ecpg where possible
Bruce Momjian's avatar
Bruce Momjian committed
861
	o Implement SQLDA
Michael Meskes's avatar
Michael Meskes committed
862
	o Fix nested C comments
Bruce Momjian's avatar
Bruce Momjian committed
863
	o %sqlwarn[6] should be 'W' if the PRECISION or SCALE value specified
864
	o Make SET CONNECTION thread-aware, non-standard?
865
	o Allow multidimensional arrays
Bruce Momjian's avatar
Bruce Momjian committed
866
	o Add internationalized message strings
Bruce Momjian's avatar
Bruce Momjian committed
867
	o Implement COPY FROM STDIN
Bruce Momjian's avatar
Bruce Momjian committed
868

Bruce Momjian's avatar
Bruce Momjian committed
869

Bruce Momjian's avatar
Bruce Momjian committed
870
* libpq
871

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
872
	o -Add a function to support Parse/DescribeStatement capability
Bruce Momjian's avatar
Bruce Momjian committed
873
	o Add PQescapeIdentifierConn()
874 875 876 877 878
	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

879
	o Allow statement results to be automatically batched to the client
880

881
	  Currently, all statement results are transferred to the libpq
882 883
	  client before libpq makes the results available to the 
	  application.  This feature would allow the application to make
884
	  use of the first result rows while the rest are transferred, or
885
	  held on the server waiting for them to be requested by libpq.
886
	  One complexity is that a statement like SELECT 1/col could error
887 888 889
	  out mid-way through the result set.


Bruce Momjian's avatar
Bruce Momjian committed
890 891
Triggers
========
892 893 894 895 896 897
* 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.

898
* Allow triggers to be disabled in only the current session.
899

900 901 902
  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
903
  TRIGGER requires a table lock so it is not ideal for this usage.
904

905
* With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
906 907 908 909

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

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
915
* Allow AFTER triggers on system tables
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
916

917 918 919 920 921
  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
922

923 924
Dependency Checking
===================
Bruce Momjian's avatar
Bruce Momjian committed
925

Bruce Momjian's avatar
Bruce Momjian committed
926 927 928
* 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
929 930 931 932

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

Bruce Momjian's avatar
Bruce Momjian committed
935 936
  This is particularly important for references to temporary tables
  in PL/PgSQL because PL/PgSQL caches query plans.  The only workaround
937 938 939
  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
940

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
941

942 943
Exotic Features
===============
944

Bruce Momjian's avatar
Bruce Momjian committed
945
* Add pre-parsing phase that converts non-ISO syntax to supported
946 947 948 949 950
  syntax

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

Bruce Momjian's avatar
Bruce Momjian committed
951
* Allow plug-in modules to emulate features from other databases
Bruce Momjian's avatar
Bruce Momjian committed
952
* SQL*Net listener that makes PostgreSQL appear as an Oracle database
Bruce Momjian's avatar
Bruce Momjian committed
953
  to clients
954
* Allow statements across databases or servers with transaction
955
  semantics
956

957
  This can be done using dblink and two-phase commit.
958

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
959
* Add the features of packages
960

961
	o  Make private objects accessible only to objects in the same schema
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
962 963 964
	o  Allow current_schema.objname to access current schema objects
	o  Add session variables
	o  Allow nested schemas
965

Bruce Momjian's avatar
Bruce Momjian committed
966 967 968
* Consider allowing control of upper/lower case folding of unquoted
  identifiers

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

Bruce Momjian's avatar
Bruce Momjian committed
971 972 973 974 975 976 977 978 979 980 981 982
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
983
* Allow SELECT ... FOR UPDATE on inherited tables
Bruce Momjian's avatar
Bruce Momjian committed
984 985 986 987 988 989 990 991 992 993 994 995
* 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
996
  http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php
Bruce Momjian's avatar
Bruce Momjian committed
997 998 999 1000 1001 1002 1003

* 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
1004
* -Add fillfactor to control reserved free space during index creation
Bruce Momjian's avatar
Bruce Momjian committed
1005 1006 1007 1008 1009 1010 1011 1012
* 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.

1013
* Allow constraint_exclusion to work for UNIONs like it does for
1014 1015
  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
1016 1017
* Allow CREATE INDEX to take an additional parameter for use with
  special index types
Bruce Momjian's avatar
Bruce Momjian committed
1018
* Consider compressing indexes by storing key values duplicated in
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1019
  several rows as a single index entry
Bruce Momjian's avatar
Bruce Momjian committed
1020

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

Bruce Momjian's avatar
Bruce Momjian committed
1023

1024 1025 1026 1027 1028
* 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
1029 1030

* Hash
1031

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

Bruce Momjian's avatar
Bruce Momjian committed
1034
	  Currently only one hash bucket can be stored on a page. Ideally
Bruce Momjian's avatar
Bruce Momjian committed
1035 1036 1037 1038 1039 1040 1041 1042
	  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
1043

Bruce Momjian's avatar
Bruce Momjian committed
1044 1045 1046
	o Add WAL logging for crash recovery
	o Allow multi-column hash indexes

1047

1048 1049
Fsync
=====
1050

1051
* Improve commit_delay handling to reduce fsync()
Bruce Momjian's avatar
Bruce Momjian committed
1052
* Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Bruce Momjian's avatar
Bruce Momjian committed
1053 1054

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

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

1061

Bruce Momjian's avatar
Bruce Momjian committed
1062 1063
Cache Usage
===========
Bruce Momjian's avatar
Bruce Momjian committed
1064

Bruce Momjian's avatar
Bruce Momjian committed
1065
* Allow free-behind capability for large sequential scans, perhaps using
Bruce Momjian's avatar
Bruce Momjian committed
1066 1067
  posix_fadvise()

Bruce Momjian's avatar
Bruce Momjian committed
1068
  Posix_fadvise() can control both sequential/random file caching and
Bruce Momjian's avatar
Bruce Momjian committed
1069 1070 1071 1072
  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.

1073 1074 1075 1076
* 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
1077 1078 1079 1080 1081
  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
1082 1083
* Add estimated_count(*) to return an estimate of COUNT(*)

1084
  This would use the planner ANALYZE statistics to return an estimated
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1085 1086
  count.

1087 1088
* Allow data to be pulled directly from indexes

Bruce Momjian's avatar
Bruce Momjian committed
1089 1090
  Currently indexes do not have enough tuple visibility information 
  to allow data to be pulled from the index without also accessing 
1091
  the heap.  One way to allow this is to set a bit on index tuples 
Bruce Momjian's avatar
Bruce Momjian committed
1092 1093
  to indicate if a tuple is currently visible to all transactions 
  when the first valid heap lookup happens.  This bit would have to 
1094 1095 1096 1097 1098 1099 1100 1101
  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
1102

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1105 1106 1107 1108
	o Parsed query tree
	o Query execute plan
	o Query results

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

1112 1113 1114 1115
  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
1116

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1117 1118 1119 1120
* 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
1121

1122 1123
Vacuum
======
Bruce Momjian's avatar
Bruce Momjian committed
1124

1125 1126
* Improve speed with indexes

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

Bruce Momjian's avatar
Bruce Momjian committed
1130 1131
* Reduce lock time during VACUUM FULL by moving tuples with read lock,
  then write lock and truncate table
1132 1133 1134 1135 1136

  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
1137 1138
* Auto-fill the free space map by scanning the buffer cache or by
  checking pages written by the background writer
1139 1140

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1143 1144 1145 1146 1147 1148
* 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
1149 1150 1151 1152
  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
1153

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1154
* -Add system view to show free space map contents
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1155 1156
* 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
1157 1158
* Allow FSM page return free space based on table clustering, to assist
  in maintaining clustering?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1159
* Consider shrinking expired tuples to just their headers
Bruce Momjian's avatar
Bruce Momjian committed
1160

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

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

Bruce Momjian's avatar
Bruce Momjian committed
1166 1167 1168 1169
  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.
1170
  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php
Bruce Momjian's avatar
Bruce Momjian committed
1171
  http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php
1172

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1173 1174
* Reuse index tuples that point to heap tuples that are not visible to 
  anyone?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1175
* Auto-vacuum
1176

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1177
	o Use free-space map information to guide refilling
Bruce Momjian's avatar
Bruce Momjian committed
1178 1179
	o %Issue log message to suggest VACUUM FULL if a table is nearly
	  empty?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1180 1181
	o Improve xid wraparound detection by recording per-table rather
	  than per-database
Bruce Momjian's avatar
Bruce Momjian committed
1182
	o Consider logging activity either to the logs or a system view
Bruce Momjian's avatar
Bruce Momjian committed
1183
	o Turn on by default
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1184

1185 1186
	  http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php

Bruce Momjian's avatar
Bruce Momjian committed
1187

1188 1189
Locking
=======
1190

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

1193

Bruce Momjian's avatar
Bruce Momjian committed
1194 1195
Startup Time Improvements
=========================
1196

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1197
* Experiment with multi-threaded backend for backend creation [thread]
1198 1199 1200

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1205 1206 1207
* 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
1208 1209 1210 1211
  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
1212

Bruce Momjian's avatar
Bruce Momjian committed
1213
* Add connection pooling
1214 1215 1216 1217

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

1219

1220 1221
Write-Ahead Log
===============
1222

1223 1224
* Eliminate need to write full pages to WAL before page modification [wal]

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

Bruce Momjian's avatar
Bruce Momjian committed
1230 1231
	o  When off, write CRC to WAL and check file system blocks
	   on recovery
Bruce Momjian's avatar
Bruce Momjian committed
1232 1233 1234 1235

	   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
1236 1237 1238 1239
	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
1240 1241 1242
	   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
1243

Bruce Momjian's avatar
Bruce Momjian committed
1244
* Allow WAL traffic to be streamed to another server for stand-by
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1245
  replication
1246
* Reduce WAL traffic so only modified values are written rather than
Bruce Momjian's avatar
Bruce Momjian committed
1247
  entire rows?
1248 1249
* 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
1250
* Allow WAL information to recover corrupted pg_controldata
1251

1252
  http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php
1253

Bruce Momjian's avatar
Bruce Momjian committed
1254 1255
* Find a way to reduce rotational delay when repeatedly writing
  last WAL page
Bruce Momjian's avatar
Bruce Momjian committed
1256

1257 1258 1259
  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.
1260

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1261 1262 1263 1264
* 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
1265
  so an abrupt operating system restart might lose a few seconds of
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1266 1267 1268 1269
  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
1270 1271
* 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
1272 1273

  Allow tables to bypass WAL writes and just fsync() dirty pages on
Bruce Momjian's avatar
Bruce Momjian committed
1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287
  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
1288

Bruce Momjian's avatar
Bruce Momjian committed
1289

1290 1291
Optimizer / Executor
====================
1292

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

Bruce Momjian's avatar
Bruce Momjian committed
1297
  Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
1298 1299
  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
1300
  MIN/MAX already does this, but not for LIMIT > 1.
1301

1302
* Precompile SQL functions to avoid overhead
Bruce Momjian's avatar
Bruce Momjian committed
1303
* Create utility to compute accurate random_page_cost value
Bruce Momjian's avatar
Bruce Momjian committed
1304
* Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1305
* Have EXPLAIN ANALYZE highlight poor optimizer estimates
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1306 1307
* Consider using hash buckets to do DISTINCT, rather than sorting

Bruce Momjian's avatar
Bruce Momjian committed
1308 1309
  This would be beneficial when there are few distinct values.  This is
  already used by GROUP BY.
Bruce Momjian's avatar
Bruce Momjian committed
1310

1311
* Log statements where the optimizer row estimates were dramatically
Bruce Momjian's avatar
Bruce Momjian committed
1312
  different from the number of rows actually found?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1313 1314 1315
* Consider compressed annealing to search for query plans

  This might replace GEQO, http://sixdemonbag.org/Djinni.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1316

Bruce Momjian's avatar
Bruce Momjian committed
1317

Bruce Momjian's avatar
Bruce Momjian committed
1318 1319
Miscellaneous Performance
=========================
1320 1321

* Do async I/O for faster random read-ahead of data
1322 1323 1324

  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
1325

Bruce Momjian's avatar
Bruce Momjian committed
1326
* Use mmap() rather than SYSV shared memory or to write WAL files?
1327 1328

  This would remove the requirement for SYSV SHM but would introduce
Bruce Momjian's avatar
Bruce Momjian committed
1329 1330
  portability issues. Anonymous mmap (or mmap to /dev/zero) is required
  to prevent I/O overhead.
Bruce Momjian's avatar
Bruce Momjian committed
1331 1332 1333

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

Bruce Momjian's avatar
Bruce Momjian committed
1334 1335 1336
  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
1337
  leading to thousands of mappings.  Another problem is that there is no
Bruce Momjian's avatar
Bruce Momjian committed
1338
  way to _prevent_ I/O to disk from the dirty shared buffers so changes
Bruce Momjian's avatar
Bruce Momjian committed
1339
  could hit disk before WAL is written.
1340

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1341
* Add a script to ask system configuration questions and tune postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
1342 1343 1344 1345 1346 1347 1348 1349 1350
* 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
1351
  could only see rows from another completed transaction. However,
Bruce Momjian's avatar
Bruce Momjian committed
1352 1353 1354 1355 1356
  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
1357
  proper visibility of the row's cmin, for example, for cursors.
Bruce Momjian's avatar
Bruce Momjian committed
1358 1359

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

Bruce Momjian's avatar
Bruce Momjian committed
1363 1364 1365
* Consider ways of storing rows more compactly on disk

	o Support a smaller header for short variable-length fields?
Bruce Momjian's avatar
Bruce Momjian committed
1366

1367 1368 1369 1370 1371 1372
	  One idea is to create zero-or-one-byte-header versions 
	  of varlena data types.  In involves setting the high-bit and 
	  0-127 length in the single-byte header, or clear the high bit
	  and store the 7-bit ASCII value in the rest of the byte.
	  The small-header versions have no alignment requirements.
	  http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php
Bruce Momjian's avatar
Bruce Momjian committed
1373

Bruce Momjian's avatar
Bruce Momjian committed
1374
	o Reduce the row header size?
1375

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1376

1377
Source Code
1378 1379
===========

Bruce Momjian's avatar
Bruce Momjian committed
1380
* Add use of 'const' for variables in source tree
Bruce Momjian's avatar
Bruce Momjian committed
1381
* Move some things from /contrib into main tree
Bruce Momjian's avatar
Bruce Momjian committed
1382
* Move some /contrib modules out to their own project sites
1383 1384 1385 1386

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

Bruce Momjian's avatar
Bruce Momjian committed
1387
* %Remove warnings created by -Wcast-align
Bruce Momjian's avatar
Bruce Momjian committed
1388
* Move platform-specific ps status display info from ps_status.c to ports
Bruce Momjian's avatar
Bruce Momjian committed
1389
* Add optional CRC checksum to heap and index pages
Bruce Momjian's avatar
Bruce Momjian committed
1390
* Improve documentation to build only interfaces (Marc)
1391
* Remove or relicense modules that are not under the BSD license, if possible
Bruce Momjian's avatar
Bruce Momjian committed
1392
* %Remove memory/file descriptor freeing before ereport(ERROR)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1393
* Acquire lock on a relation before building a relcache entry for it
Bruce Momjian's avatar
Bruce Momjian committed
1394 1395
* %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
1396
* Allow cross-compiling by generating the zic database on the target system
Neil Conway's avatar
Neil Conway committed
1397
* Improve NLS maintenance of libpgport messages linked onto applications
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1398
* Allow ecpg to work with MSVC and BCC
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1399
* Add xpath_array() to /contrib/xml2 to return results as an array
Bruce Momjian's avatar
Bruce Momjian committed
1400 1401 1402 1403 1404
* 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
1405
* -Allow installing to directories containing spaces
Bruce Momjian's avatar
Bruce Momjian committed
1406 1407 1408 1409 1410

  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
1411

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1412
* Fix sgmltools so PDFs can be generated with bookmarks
Neil Conway's avatar
Neil Conway committed
1413
* -%Clean up compiler warnings (especially with gcc version 4)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1414 1415
* Use UTF8 encoding for NLS messages so all server encodings can
  read them properly
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1416
* Update Bonjour to work with newer cross-platform SDK
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1417
* -Remove BeOS and QNX-specific code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1418 1419
* 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
1420 1421 1422 1423
* 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
1424

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1425
* Consider detoasting keys before sorting
Bruce Momjian's avatar
Bruce Momjian committed
1426 1427
* Consider GnuTLS if OpenSSL license becomes a problem

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

Bruce Momjian's avatar
Bruce Momjian committed
1430

1431
* Win32
1432

1433 1434 1435 1436 1437 1438 1439
	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
1440 1441
	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
1442
	o Fix problem with shared memory on the Win32 Terminal Server
1443 1444
	o Improve signal handling

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

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1447 1448 1449 1450
	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
1451 1452 1453
	  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
1454

Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1455
	o -Port contrib/xml2
Bruce Momjian's avatar
Bruce Momjian committed
1456
	o Check WSACancelBlockingCall() for interrupts [win32intr]
Bruce Momjian's avatar
Bruce Momjian committed
1457

Bruce Momjian's avatar
Bruce Momjian committed
1458

Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1459
* Wire Protocol Changes
1460

1461
	o Allow dynamic character set handling
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1462
	o Add decoded type, length, precision
1463
	o Use compression?
Bruce Momjian's avatar
Bruce Momjian committed
1464
	o Update clients to use data types, typmod, schema.table.column names
1465
	  of result sets using new statement protocol
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1466

1467

1468 1469 1470
Features We Do _Not_ Want
=========================

Bruce Momjian's avatar
Bruce Momjian committed
1471
* All backends running as threads in a single process (not wanted)
1472 1473 1474 1475 1476

  This eliminates the process protection we get from the current setup.
  Thread creation is usually the same overhead as process creation on
  modern systems, so it seems unwise to use a pure threaded model.

Bruce Momjian's avatar
Bruce Momjian committed
1477
* Optimizer hints (not wanted)
1478 1479 1480 1481 1482

  Optimizer hints are used to work around problems in the optimizer.  We
  would rather have the problems reported and fixed.
  http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php

Bruce Momjian's avatar
Bruce Momjian committed
1483 1484 1485 1486 1487 1488
* Allow AS in "SELECT col AS label" to be optional (not wanted)

  Because we support postfix operators, it isn't possible to make AS
  optional and continue to use bison.
  http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php

1489

1490 1491 1492 1493 1494
---------------------------------------------------------------------------


Developers who have claimed items are:
--------------------------------------
Bruce Momjian's avatar
Bruce Momjian committed
1495
* Alvaro is Alvaro Herrera <alvherre@dcc.uchile.cl>
Bruce Momjian's avatar
Bruce Momjian committed
1496
* Andrew is Andrew Dunstan <andrew@dunslane.net>
Bruce Momjian's avatar
Bruce Momjian committed
1497
* Bruce is Bruce Momjian <bruce@momjian.us> of EnterpriseDB
Bruce Momjian's avatar
Bruce Momjian committed
1498 1499 1500
* 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
1501
* David is David Fetter <david@fetter.org>
Bruce Momjian's avatar
Bruce Momjian committed
1502
* Fabien is Fabien Coelho <coelho@cri.ensmp.fr>
Bruce Momjian's avatar
Bruce Momjian committed
1503 1504
* 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
1505
* Jan is Jan Wieck <JanWieck@Yahoo.com> of Afilias, Inc.
Bruce Momjian's avatar
Bruce Momjian committed
1506
* Joe is Joe Conway <mail@joeconway.com>
1507
* Karel is Karel Zak <zakkr@zf.jcu.cz>
Bruce Momjian's avatar
Fix :  
Bruce Momjian committed
1508
* Magnus is Magnus Hagander <mha@sollentuna.net>
Bruce Momjian's avatar
Bruce Momjian committed
1509
* Marc is Marc Fournier <scrappy@hub.org> of PostgreSQL, Inc.
Bruce Momjian's avatar
Bruce Momjian committed
1510
* Matthew T. O'Connor <matthew@zeut.net>
Bruce Momjian's avatar
Bruce Momjian committed
1511
* Michael is Michael Meskes <meskes@postgresql.org> of Credativ
Bruce Momjian's avatar
Bruce Momjian committed
1512
* Neil is Neil Conway <neilc@samurai.com>
Bruce Momjian's avatar
Bruce Momjian committed
1513
* Oleg is Oleg Bartunov <oleg@sai.msu.su>
Bruce Momjian's avatar
Bruce Momjian committed
1514
* Pavel is Pavel Stehule <pavel.stehule@hotmail.com>
1515
* Peter is Peter Eisentraut <peter_e@gmx.net>
Bruce Momjian's avatar
Bruce Momjian committed
1516
* Philip is Philip Warner <pjw@rhyme.com.au> of Albatross Consulting Pty. Ltd.
Bruce Momjian's avatar
Bruce Momjian committed
1517
* Rod is Rod Taylor <pg@rbt.ca>
Bruce Momjian's avatar
Bruce Momjian committed
1518
* Simon is Simon Riggs <simon@2ndquadrant.com>
Bruce Momjian's avatar
Bruce Momjian committed
1519
* Stephan is Stephan Szabo <sszabo@megazone23.bigpanda.com>
Bruce Momjian's avatar
Bruce Momjian committed
1520
* Tatsuo is Tatsuo Ishii <ishii@sraoss.co.jp> of SRA OSS, Inc. Japan
Bruce Momjian's avatar
Bruce Momjian committed
1521
* Teodor is Teodor Sigaev <teodor@sigaev.ru>
Bruce Momjian's avatar
Bruce Momjian committed
1522
* Tom is Tom Lane <tgl@sss.pgh.pa.us> of Red Hat