TODO.html 72.7 KB
Newer Older
1 2 3 4
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
Bruce Momjian's avatar
Bruce Momjian committed
5
<title>PostgreSQL TODO List</title>
6 7 8
<meta name="generator" content="HTML::TextToHTML v2.25"/>
</head>
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
Bruce Momjian's avatar
Bruce Momjian committed
9 10
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer:     Bruce Momjian (<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>)<br/>
11
Last updated:           Mon Sep 18 10:56:04 EDT 2006
Bruce Momjian's avatar
Bruce Momjian committed
12
</p>
Bruce Momjian's avatar
Bruce Momjian committed
13 14
<p>The most recent version of this document can be viewed at<br/>
<a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
15
</p>
Bruce Momjian's avatar
Bruce Momjian committed
16
<p><strong>A hyphen, "-", marks changes that will appear in the upcoming 8.2 release.</strong><br/>
Bruce Momjian's avatar
Bruce Momjian committed
17
<strong>A percent sign, "%", marks items that are easier to implement.</strong>
18 19 20 21 22 23 24
</p>
<p>Bracketed items, "[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]", have more detail.
</p>
<p>This list contains all known PostgreSQL bugs and feature requests. If<br/>
you would like to work on an item, please read the Developer's FAQ<br/>
first.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
25
<h1><a name="section_2">Administration</a></h1>
26 27

<ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
28
  <li>-<em>Make postmater and postgres options distinct so the postmaster -o</em>
Bruce Momjian's avatar
Bruce Momjian committed
29
  option is no longer needed
Bruce Momjian's avatar
Bruce Momjian committed
30
  </li><li>-<em>Allow pooled connections to list all prepared statements</em>
31
<p>  This would allow an application inheriting a pooled connection to know
32
  the statements prepared in the current session.
33
</p>
Bruce Momjian's avatar
Bruce Momjian committed
34 35
  </li><li>Allow major upgrades without dump/reload, perhaps using pg_upgrade 
  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pg_upgrade">pg_upgrade</a>]
Bruce Momjian's avatar
Bruce Momjian committed
36
  </li><li>Check for unreferenced table files created by transactions that were
37
  in-progress when the server terminated abruptly
Bruce Momjian's avatar
Bruce Momjian committed
38 39
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00096.php</a>
</p>
Bruce Momjian's avatar
Bruce Momjian committed
40 41
  </li><li>Allow administrators to safely terminate individual sessions either
  via an SQL function or SIGTERM 
Bruce Momjian's avatar
Bruce Momjian committed
42 43 44 45
<p>  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.
46
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</a>
47
</p>
Bruce Momjian's avatar
Bruce Momjian committed
48
  </li><li>%Set proper permissions on non-system schemas during db creation
49 50 51
<p>  Currently all schemas are owned by the super-user because they are
  copied from the template1 database.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
52 53 54
  </li><li>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
55
  </li><li>Add function to report the time of the most recent server reload
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
56 57 58
  </li><li>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
59 60 61
  </li><li>Allow log_min_messages to be specified on a per-module basis
<p>  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
Add:  
Bruce Momjian committed
64
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
65
  </li><li>-<em>Re-enable the GUC full_page_writes in 8.2 when reliability issues have</em>
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
  </li><li>Simplify ability to create partitioned tables
<p>  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.
</p>
  </li><li>Allow auto-selection of partitioned tables for min/max() operations
74 75 76 77 78 79 80 81 82
  </li><li>Improve replication solutions
  <ul>
    <li>Load balancing
<p>          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.
</p>
    </li><li>Allow replication over unreliable or non-persistent links
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
83 84
  </li><li>Configuration files
  <ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
85
    <li>-<em>Add "include file" functionality in postgresql.conf</em>
Bruce Momjian's avatar
Bruce Momjian committed
86
    </li><li>Allow commenting of variables in postgresql.conf to restore them
Bruce Momjian's avatar
Bruce Momjian committed
87
          to defaults
Bruce Momjian's avatar
Bruce Momjian committed
88 89 90
<p>          Currently, if a variable is commented out, it keeps the
          previous uncommented value until a server restarted.
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
91
    </li><li>-<em>Allow per-database permissions to be set via GRANT</em>
92 93
<p>          Allow database connection checks based on GRANT rules in
          addition to the existing access checks in pg_hba.conf.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
94 95 96 97 98 99 100 101
</p>
    </li><li>Allow pg_hba.conf to specify host names along with IP addresses
<p>          Host name lookup could occur when the postmaster reads the
          pg_hba.conf file, or when the backend starts.  Another
          solution would be to reverse lookup the connection IP and
          check that hostname against the host names in pg_hba.conf.
          We could also then check that the host name maps to the IP
          address.
Bruce Momjian's avatar
Bruce Momjian committed
102
</p>
Bruce Momjian's avatar
Bruce Momjian committed
103
    </li><li>%Allow postgresql.conf file values to be changed via an SQL
Bruce Momjian's avatar
Bruce Momjian committed
104
          API, perhaps using SET GLOBAL
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
105
    </li><li>Allow the server to be stopped/restarted via an SQL API
Bruce Momjian's avatar
Bruce Momjian committed
106 107
    </li><li>-<em>Issue a warning if a change-on-restart-only postgresql.conf value</em>
          is modified  and the server config files are reloaded
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
108
    </li><li>Mark change-on-restart-only values in postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130
  </li></ul>
  </li><li>Tablespaces
  <ul>
    <li>Allow a database in tablespace t1 with tables created in
          tablespace t2 to be used as a template for a new database created
          with default tablespace t2
<p>          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.
</p>
    </li><li>Allow reporting of which objects are in which tablespaces
<p>          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.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
131
    </li><li>%Add a GUC variable to control the tablespace for temporary objects
Bruce Momjian's avatar
Bruce Momjian committed
132 133 134 135
          and sort files
<p>          It could start with a random tablespace from a supplied list and
          cycle through the list.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
136
    </li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
Bruce Momjian's avatar
Bruce Momjian committed
137
          structure on the recovery computer is different from the original
Bruce Momjian's avatar
Bruce Momjian committed
138
    </li><li>Allow per-tablespace quotas
Bruce Momjian's avatar
Bruce Momjian committed
139
  </li></ul>
140
  </li><li>Point-In-Time Recovery (PITR)
Bruce Momjian's avatar
Bruce Momjian committed
141
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
142
    <li>Add command to archive partially filled write-ahead logs? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
Bruce Momjian's avatar
Bruce Momjian committed
143 144
<p>            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
145
            of a disk failure.
Bruce Momjian's avatar
Bruce Momjian committed
146
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
147
    </li><li>-Automatically force archiving of partially-filled WAL files when
Bruce Momjian's avatar
Bruce Momjian committed
148
            pg_stop_backup() is called or the server is stopped
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
149
    </li><li>-Add reporting of the current WAL file and offset, perhaps as
Bruce Momjian's avatar
Bruce Momjian committed
150
            part of partial log file archiving
Bruce Momjian's avatar
Bruce Momjian committed
151
    </li><li>%Create dump tool for write-ahead logs for use in determining
Bruce Momjian's avatar
Bruce Momjian committed
152
            transaction id for point-in-time recovery
153
    </li><li>Allow a warm standby system to also allow read-only statements
Bruce Momjian's avatar
Bruce Momjian committed
154 155 156 157 158 159
            [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p>            This is useful for checking PITR recovery.
</p>
    </li><li>Allow the PITR process to be debugged and data examined
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
160
<h1><a name="section_3">Monitoring</a></h1>
Bruce Momjian's avatar
Bruce Momjian committed
161 162 163 164 165 166

<ul>
  <li>Allow server log information to be output as INSERT statements
<p>  This would allow server log information to be easily loaded into
  a database for analysis.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
167
  </li><li>%Add ability to monitor the use of temporary sort files
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
168
  </li><li>-<em>Allow server logs to be remotely read and removed using SQL commands</em>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
169
  </li><li>-<em>Allow protocol-level BIND parameter values to be logged</em>
170
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
171
<h1><a name="section_4">Data Types</a></h1>
172 173

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
174 175 176
  <li>Improve the MONEY data type
<p>  Change the MONEY data type to use DECIMAL internally, with special
  locale-aware output formatting.
Bruce Momjian's avatar
Bruce Momjian committed
177
  <a href="http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php">http://archives.postgresql.org/pgsql-general/2005-08/msg01432.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
178
</p>
179
  </li><li>Change NUMERIC to enforce the maximum precision
Bruce Momjian's avatar
Bruce Momjian committed
180 181 182 183 184 185 186 187 188 189 190 191
  </li><li>Add NUMERIC division operator that doesn't round?
<p>  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 &gt; 10:
</p>
</li></ul>
<p>    SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6;
</p>
<p>  The positive modulus result returned by NUMERICs might be considered<br/>
  inaccurate, in one sense.
</p>
<ul>
192
  <li>Fix data types where equality comparison isn't intuitive, e.g. box
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
193 194
  </li><li>-<em>Zero umasked bits in conversion from INET cast to CIDR</em>
  </li><li>-<em>Prevent INET cast to CIDR from dropping netmask, SELECT '<a href="telnet://1.1.1.1">1.1.1.1</a>'::inet::cidr</em>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
195
  </li><li>-<em>Allow INET + INT8 to increment the host part of the address or</em>
Bruce Momjian's avatar
Bruce Momjian committed
196
  throw an error on overflow
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
197
  </li><li>-<em>Add 'tid != tid ' operator for use in corruption recovery</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
198 199
  </li><li>Allow user-defined types to specify a type modifier at table creation
  time
Bruce Momjian's avatar
Bruce Momjian committed
200 201 202
  </li><li>Allow user-defined types to accept 'typmod' parameters
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php">http://archives.postgresql.org/pgsql-hackers/2005-08/msg01142.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00012.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
203
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00149.php</a>
Bruce Momjian's avatar
>  
Bruce Momjian committed
204 205 206
</p>
  </li><li>Add support for public SYNONYMs
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00519.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
207 208 209
</p>
  </li><li>Fix CREATE CAST on DOMAINs
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php">http://archives.postgresql.org/pgsql-hackers/2006-05/msg00072.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
210
</p>
Bruce Momjian's avatar
Bruce Momjian committed
211
  </li><li>Add Globally/Universally Unique Identifier (GUID/UUID)
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
212 213
  </li><li>Add support for SQL-standard GENERATED/IDENTITY columns
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php">http://archives.postgresql.org/pgsql-hackers/2006-07/msg00543.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
214 215 216
</p>
  </li><li>Support a data type with specific enumerated values (ENUM)
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
217 218 219
</p>
  </li><li>Improve XML support
<p>  <a href="http://developer.postgresql.org/index.php/XML_Support">http://developer.postgresql.org/index.php/XML_Support</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
220
</p>
221
  </li><li>Dates and Times
222
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
223
    <li>Allow infinite dates and intervals just like infinite timestamps
224 225
    </li><li>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
226
    </li><li>-<em>Allow customization of the known set of TZ names (generalize the</em>
227 228 229 230
          present australian_timezones hack)
    </li><li>Allow TIMESTAMP WITH TIME ZONE to store the original timezone
          information, either zone name or offset from UTC [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?timezone">timezone</a>]
<p>          If the TIMESTAMP value is stored with a time zone name, interval 
Bruce Momjian's avatar
Bruce Momjian committed
231
          computations should adjust based on the time zone rules.
232
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
233
    </li><li>-<em>Allow timezone names in SQL strings, '2006-05-24 21:11</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
234
           Americas/New_York'::timestamptz
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
235
    </li><li>Fix SELECT '0.01 years'::interval, '0.01 months'::interval
Bruce Momjian's avatar
Bruce Momjian committed
236 237 238 239 240 241 242 243 244 245 246 247
    </li><li>Add a GUC variable to allow output of interval values in ISO8601 
          format
    </li><li>Improve timestamptz subtraction to be DST-aware
<p>          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.
</p>
    </li><li>Fix interval display to support values exceeding 2^31 hours
    </li><li>Add overflow checking to timestamp and interval arithmetic    
248
    </li><li>Add ISO INTERVAL handling
249 250
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
251 252
<p>                  <a href="http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php">http://archives.postgresql.org/pgsql-hackers/2006-01/msg00250.php</a><br/>
                  <a href="http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php">http://archives.postgresql.org/pgsql-bugs/2006-04/msg00248.php</a>
253 254 255
</p>
<ul>
  <li>-<em>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO </em>
256
                  SECOND
257
  </li><li>Support ISO INTERVAL syntax if units cannot be determined from
258
                  the string, and are supplied after the string
Bruce Momjian's avatar
Bruce Momjian committed
259 260 261 262 263
<p>                  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'.
264 265 266
</p>
<p>                  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
267 268 269 270 271 272 273 274 275 276
                  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'.
</p>
<p>                  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.
277
</p>
278 279
  </li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
  </li><li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
280
                  INTERVAL MONTH), and this should return '12 months'
281
  </li><li>Round or truncate values to the requested precision, e.g.
282
                  INTERVAL '11 months' AS YEAR should return one or zero
283
  </li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
284
  <ul>
285 286 287 288
    <li>Arrays
    <ul>
      <li>-<em>Allow NULLs in arrays</em>
      </li><li>Delay resolution of array expression's data type so assignment
289
          coercion can be performed on empty array expressions
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
290 291
      </li><li>Add support for arrays of domains
      </li><li>Add support for arrays of complex types
292 293 294 295 296 297
    </li></ul>
    </li><li>Binary Data
    <ul>
      <li>Improve vacuum of large objects, like /contrib/vacuumlo?
      </li><li>Add security checking for large objects
      </li><li>Auto-delete large objects when referencing row is deleted
Bruce Momjian's avatar
Bruce Momjian committed
298 299
<p>          /contrib/lo offers this functionality.
</p>
300
      </li><li>Allow read/write into TOAST values like large objects
301
<p>          This requires the TOAST column to be stored EXTERNAL.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
302
</p>
303
      </li><li>Add API for 64-bit large object access
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
304
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</a>
305
</p>
306
    </li></ul>
307 308
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
309
<h1><a name="section_5">Functions</a></h1>
Bruce Momjian's avatar
Bruce Momjian committed
310 311

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
312
  <li>Allow INET subnet tests using non-constants to be indexed
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
313
  </li><li>-<em>Add transaction_timestamp(), statement_timestamp(), clock_timestamp()</em>
Bruce Momjian's avatar
Bruce Momjian committed
314 315 316 317 318 319
  functionality
<p>  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.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
320
  </li><li>%Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Bruce Momjian's avatar
Bruce Momjian committed
321
  pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
322 323
<p>  These would be for application use, not for use by pg_dump.
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
324
  </li><li>-<em>Allow to_char() to print localized month names</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
325
  </li><li>Allow to_date() and to_timestamp() accept localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
326 327 328 329 330 331
  </li><li>Add missing parameter handling in to_char()
</li></ul>
<p>        <a href="http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php">http://archives.postgresql.org/pgsql-hackers/2005-12/msg00948.php</a>
</p>
<ul>
  <li>Allow functions to have a schema search path specified at creation time
Bruce Momjian's avatar
Bruce Momjian committed
332 333 334 335 336 337 338 339 340 341 342 343 344 345
  </li><li>Allow substring/replace() to get/set bit values
  </li><li>Allow to_char() on interval values to accumulate the highest unit
  requested
<p>  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.
</p>
  <ul>
    <li>to_char(INTERVAL '1 hour 5 minutes', 'MI') =&gt; 65
    </li><li>to_char(INTERVAL '43 hours 20 minutes', 'MI' ) =&gt; 2600 
    </li><li>to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') =&gt; 0:1:19:20
    </li><li>to_char(INTERVAL '3 years 5 months','MM') =&gt; 41
  </li></ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
346
  </li><li>-<em>Add sleep() function, remove from regress.c</em>
Bruce Momjian's avatar
Bruce Momjian committed
347
  </li><li>-<em>Allow user-defined functions retuning a domain value to enforce domain</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
348
  constraints
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
349
  </li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
350
  </li><li>Allow inlining of set-returning functions
Bruce Momjian's avatar
Bruce Momjian committed
351
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
352
<h1><a name="section_6">Multi-Language Support</a></h1>
353 354 355 356

<ul>
  <li>Add NCHAR (as distinguished from ordinary varchar),
  </li><li>Allow locale to be set at database creation
Bruce Momjian's avatar
Bruce Momjian committed
357 358 359 360
<p>  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.
361
</p>
Bruce Momjian's avatar
Bruce Momjian committed
362
  </li><li>Allow encoding on a per-column basis optionally using the ICU library:
363
<p>  Right now only one encoding is allowed per database.  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?locale">locale</a>]
364
  <a href="http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php">http://archives.postgresql.org/pgsql-hackers/2005-03/msg00932.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
365 366
  <a href="http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php">http://archives.postgresql.org/pgsql-patches/2005-08/msg00309.php</a>
  <a href="http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00233.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
367
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php</a>
368
</p>
369
  </li><li>Add CREATE COLLATE?  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?locale">locale</a>]
370
  </li><li>Support multiple simultaneous character sets, per SQL92
Bruce Momjian's avatar
Bruce Momjian committed
371
  </li><li>Improve UTF8 combined character handling?
372 373
  </li><li>Add octet_length_server() and octet_length_client()
  </li><li>Make octet_length_client() the same as octet_length()?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
374
  </li><li>Fix problems with wrong runtime encoding conversion for NLS message files
Bruce Momjian's avatar
Bruce Momjian committed
375 376
  </li><li>Add URL to more complete multi-byte regression tests
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php">http://archives.postgresql.org/pgsql-hackers/2005-07/msg00272.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
377 378 379 380
</p>
  </li><li>Fix ILIKE and regular expressions to handle case insensitivity
  properly in multibyte encodings
<p>  <a href="http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php">http://archives.postgresql.org/pgsql-bugs/2005-10/msg00001.php</a>
381
  <a href="http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php">http://archives.postgresql.org/pgsql-patches/2005-11/msg00173.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
382
</p>
383
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
384
<h1><a name="section_7">Views / Rules</a></h1>
385 386

<ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
387
  <li>Automatically create rules on views so they are updateable, per SQL99
388
<p>  We can only auto-create rules for simple views.  For more complex
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
389
  cases users will still have to write rules manually.
Bruce Momjian's avatar
Bruce Momjian committed
390
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php</a>
391 392 393
</p>
  </li><li>Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
  </li><li>Allow NOTIFY in rules involving conditionals
Bruce Momjian's avatar
Bruce Momjian committed
394
  </li><li>Allow VIEW/RULE recompilation when the underlying tables change
Bruce Momjian's avatar
Bruce Momjian committed
395 396 397 398
<p>  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.
</p>
399
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
400
<h1><a name="section_8">SQL Commands</a></h1>
401 402

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
403
  <li>Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
404
  </li><li>Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
Bruce Momjian's avatar
Bruce Momjian committed
405
  </li><li>%Allow SET CONSTRAINTS to be qualified by schema/table name
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
406
  </li><li>-<em>Allow TRUNCATE ... CASCADE/RESTRICT</em>
Bruce Momjian's avatar
Bruce Momjian committed
407 408
<p>  This is like DELETE CASCADE, but truncates.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
409
  </li><li>%Add a separate TRUNCATE permission
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
410 411 412
<p>  Currently only the owner can TRUNCATE a table because triggers are not
  called, and the table is locked in exclusive mode.
</p>
413 414 415 416 417 418 419 420
  </li><li>Allow PREPARE of cursors
  </li><li>Allow finer control over the caching of prepared query plans
<p>  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.
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
421 422
  </li><li>Invalidate prepared queries, like INSERT, when the table definition
  is altered
423 424 425 426 427 428 429 430
  </li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
<p>  Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
  such information in memory would improve performance.
</p>
  </li><li>Add optional textual message to NOTIFY
<p>  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
Add:  
Bruce Momjian committed
431
</p>
432
  </li><li>Add a GUC variable to warn about non-standard SQL usage in queries
433
  </li><li>Add SQL-standard MERGE command, typically used to merge two tables
Bruce Momjian's avatar
Bruce Momjian committed
434
  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
435 436 437 438 439
<p>  This is similar to UPDATE, then for unmatched rows, INSERT.
  Whether concurrent access allows modifications which could cause
  row loss is implementation independent.
</p>
  </li><li>Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
Bruce Momjian's avatar
Bruce Momjian committed
440
  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
Bruce Momjian's avatar
Bruce Momjian committed
441
<p>  To implement this cleanly requires that the table have a unique index
442 443 444
  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
445
</p>
446 447
  </li><li>Add NOVICE output level for helpful messages like automatic sequence/index
  creation
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
448
  </li><li>-<em>Add COMMENT ON for all cluster global objects (roles, databases</em>
449
  and tablespaces)
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
450
  </li><li>-<em>Make row-wise comparisons work per SQL spec</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
451 452 453 454
<p>  Right now, '(a, b) &lt; (1, 2)' is processed as 'a &lt; 1 and b &lt; 2', but
  the SQL standard requires it to be processed as a column-by-column
  comparison, so the proper comparison is '(a &lt; 1) OR (a = 1 AND b &lt; 2)'.
</p>
455
  </li><li>Add RESET CONNECTION command to reset all session state
456
<p>  This would include resetting of all variables (RESET ALL), dropping of
457 458 459 460
  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
461 462
  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 
463
  notify the protocol when a RESET CONNECTION command is used.
Bruce Momjian's avatar
Bruce Momjian committed
464
  <a href="http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php">http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php</a>
465
</p>
466
  </li><li>Add GUC to issue notice about statements that use unjoined tables
467
  </li><li>Allow EXPLAIN to identify tables that were skipped because of 
468
  constraint_exclusion
469
  </li><li>Allow EXPLAIN output to be more easily processed by scripts
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
470 471 472 473 474 475 476 477
  </li><li>-<em>Enable escape_string<u>warning and standard</u>conforming_strings</em>
  </li><li>Make standard_conforming_strings the default in 8.3?
<p>  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.
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
478
  </li><li>Simplify dropping roles that have objects in several databases
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
479
  </li><li>Allow COMMENT ON to accept an expression rather than just a string
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
480 481
  </li><li>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
482
  </li><li>Make CLUSTER preserve recently-dead tuples per MVCC requirements
Bruce Momjian's avatar
Bruce Momjian committed
483
  </li><li>Add SQL99 WITH clause to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
484
  </li><li>Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
485 486 487 488
  </li><li>Add DEFAULT .. AS OWNER so permission checks are done as the table
  owner
<p>  This would be useful for SERIAL nextval() calls and CHECK constraints.
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
489 490
  </li><li>Add a GUC to control whether BEGIN inside a transcation should abort
  the transaction.
Bruce Momjian's avatar
Bruce Momjian committed
491
  </li><li>Allow DISTINCT to work in multiple-argument aggregate calls
Bruce Momjian's avatar
Bruce Momjian committed
492 493
  </li><li>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
494
  </li><li>Implement SQL:2003 window functions
495 496 497 498 499 500
  </li><li>CREATE
  <ul>
    <li>Allow CREATE TABLE AS to determine column lengths for complex
          expressions like SELECT col1 || col2
    </li><li>Use more reliable method for CREATE DATABASE to get a consistent
          copy of db?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
501
    </li><li>-<em>Add ON COMMIT capability to CREATE TABLE AS ... SELECT</em>
502 503 504
  </li></ul>
  </li><li>UPDATE
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
505
    <li>-<em>Allow an alias to be provided for the target table in</em>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
506
          UPDATE/DELETE (Neil)
Bruce Momjian's avatar
Bruce Momjian committed
507 508 509 510
    </li><li>-<em>Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating</em>
          multiple columns
    </li><li>Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php">http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php</a>
511
</p>
512
  </li></ul>
513 514
  </li><li>ALTER
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
515
    <li>%Have ALTER TABLE RENAME rename SERIAL sequence names
Bruce Momjian's avatar
Bruce Momjian committed
516
    </li><li>Add ALTER DOMAIN to modify the underlying data type
Bruce Momjian's avatar
Bruce Momjian committed
517
    </li><li>%Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
518
<p>          <a href="http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php">http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php</a>
519
</p>
Bruce Momjian's avatar
Bruce Momjian committed
520
    </li><li>%Allow ALTER TABLE to change constraint deferrability and actions
Bruce Momjian's avatar
Bruce Momjian committed
521
    </li><li>Add missing object types for ALTER ... SET SCHEMA
522
    </li><li>Allow ALTER TABLESPACE to move to different directories
523
    </li><li>Allow databases to be moved to different tablespaces
524 525
    </li><li>Allow moving system tables to other tablespaces, where possible
<p>          Currently non-global system tables must be in the default database
526
          tablespace. Global system tables can never be moved.
527
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
528
    </li><li>Prevent parent tables from altering or dropping constraints
529 530 531 532
          like CHECK that are inherited by child tables unless CASCADE
          is used
    </li><li>%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
533
    </li><li>-<em>Add ALTER TABLE tab INHERIT / NO INHERIT  parent</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
534
    </li><li>Have ALTER INDEX update the name of a constraint using that index
Bruce Momjian's avatar
Bruce Momjian committed
535
    </li><li>Add ALTER TABLE RENAME CONSTRAINT, update index name also
536 537 538 539 540 541
  </li></ul>
  </li><li>CLUSTER
  <ul>
    <li>Automatically maintain clustering on a table
<p>          This might require some background daemon to maintain clustering
          during periods of low usage. It might also require tables to be only
Bruce Momjian's avatar
Bruce Momjian committed
542
          partially filled for easier reorganization.  Another idea would
543 544 545 546
          be to create a merged heap/index data file so an index lookup would
          automatically access the heap data too.  A third idea would be to
          store heap rows in hashed groups, perhaps using a user-supplied
          hash function.
Bruce Momjian's avatar
Bruce Momjian committed
547
          <a href="http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php">http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php</a>
548
</p>
Bruce Momjian's avatar
Bruce Momjian committed
549
    </li><li>%Add default clustering to system tables
550 551 552 553 554 555 556 557 558 559
<p>          To do this, determine the ideal cluster index for each system
          table and set the cluster setting during initdb.
</p>
  </li></ul>
  </li><li>COPY
  <ul>
    <li>Allow COPY to report error lines and continue
<p>          This requires the use of a savepoint before each COPY line is
          processed, with ROLLBACK on COPY failure.
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
560
    </li><li>-<em>Have COPY return the number of rows loaded/unloaded?</em>
Bruce Momjian's avatar
Bruce Momjian committed
561 562
    </li><li>Allow COPY on a newly-created table to skip WAL logging
<p>          On crash recovery, the table involved in the COPY would
Bruce Momjian's avatar
Bruce Momjian committed
563
          be removed or have its heap and index files truncated.  One
Bruce Momjian's avatar
Bruce Momjian committed
564 565 566
          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
567
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
568
    </li><li>-<em>Allow COPY (SELECT ...) TO 'filename'</em>
569
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
570 571 572
  </li><li>GRANT/REVOKE
  <ul>
    <li>Allow column-level privileges
Bruce Momjian's avatar
Bruce Momjian committed
573
    </li><li>%Allow GRANT/REVOKE permissions to be applied to all schema objects
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
574
          with one command
Bruce Momjian's avatar
Bruce Momjian committed
575 576 577 578
<p>          The proposed syntax is:
</p><p>                GRANT SELECT ON ALL TABLES IN public TO phpuser;
                GRANT SELECT ON NEW TABLES IN public TO phpuser;
</p>
Bruce Momjian's avatar
Bruce Momjian committed
579
    </li><li>Allow GRANT/REVOKE permissions to be inherited by objects based on
Bruce Momjian's avatar
Bruce Momjian committed
580
          schema permissions
Bruce Momjian's avatar
Bruce Momjian committed
581
    </li><li>Allow SERIAL sequences to inherit permissions from the base table?
Bruce Momjian's avatar
Bruce Momjian committed
582
  </li></ul>
583 584 585 586 587 588 589 590 591
  </li><li>CURSOR
  <ul>
    <li>Allow UPDATE/DELETE WHERE CURRENT OF cursor
<p>          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.
</p>
    </li><li>Prevent DROP TABLE from dropping a row referenced by its own open
Bruce Momjian's avatar
Bruce Momjian committed
592
          cursor?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
593
    </li><li>-<em>Allow pooled connections to list all open WITH HOLD cursors</em>
594 595 596 597 598 599 600
<p>          Because WITH HOLD cursors exist outside transactions, this allows
          them to be listed so they can be closed.
</p>
  </li></ul>
  </li><li>INSERT
  <ul>
    <li>Allow INSERT/UPDATE of the system-generated oid value for a row
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
601
    </li><li>-<em>Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)</em>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
602 603
    </li><li>-<em>Allow INSERT/UPDATE ... RETURNING new.col or old.col</em>
    </li><li>In rules, allow VALUES() to contain a mixture of 'old' and 'new'
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
604
          references
605
  </li></ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
606
  </li><li>SHOW/SET
607
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
608
    <li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
609
          ANALYZE, and CLUSTER
Bruce Momjian's avatar
Bruce Momjian committed
610
    </li><li>Add SET PATH for schemas?
611 612 613
<p>          This is basically the same as SET search_path.
</p>
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
614 615 616 617 618 619
  </li><li>Referential Integrity
  <ul>
    <li>Add MATCH PARTIAL referential integrity
    </li><li>Change foreign key constraint for array -&gt; element to mean element
          in array?
    </li><li>Enforce referential integrity for system tables
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
620 621 622 623
    </li><li>Fix problem when cascading referential triggers make changes on
          cascaded tables, seeing the tables in an intermediate state
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php</a>
          <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00174.php</a>
624 625 626 627 628 629
</p>
    </li><li>Allow DEFERRABLE and end-of-statement UNIQUE constraints?
<p>          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
630
          <a href="http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html">http://people.planetpostgresql.org/greg/index.php?/archives/2006/06/10.html</a>
631
          <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01458.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
632
</p>
Bruce Momjian's avatar
Bruce Momjian committed
633
  </li></ul>
634
  </li><li>Server-Side Languages
635
  <ul>
636 637 638 639
    <li>PL/pgSQL
    <ul>
      <li>Fix RENAME to work on variables other than OLD/NEW
      </li><li>Allow function parameters to be passed by name,
Bruce Momjian's avatar
Fix:  
Bruce Momjian committed
640
                  get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
Bruce Momjian's avatar
Bruce Momjian committed
641
      </li><li>Add Oracle-style packages  (Pavel)
Bruce Momjian's avatar
Bruce Momjian committed
642
<p>                  A package would be a schema with session-local variables,
Bruce Momjian's avatar
Bruce Momjian committed
643
                  public/private functions, and initialization functions.  It
Bruce Momjian's avatar
Bruce Momjian committed
644 645 646
                  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
647
                  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00384.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
648
</p>
649 650 651 652 653 654 655 656 657 658
      </li><li>Allow handling of %TYPE arrays, e.g. tab.col%TYPE[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]
      </li><li>Allow listing of record column names, and access to
                  record columns via variables, e.g. columns := r.(*),
                  tval2 := r.(colname)
<p>                  <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00458.php</a>
                  <a href="http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php">http://archives.postgresql.org/pgsql-patches/2006-05/msg00302.php</a>
                  <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00031.php</a>
</p>
      </li><li>Add MOVE
      </li><li>Add single-step debugging of functions
Bruce Momjian's avatar
Bruce Momjian committed
659 660 661 662
      </li><li>Add support for WITH HOLD and SCROLL cursors
<p>                  PL/pgSQL cursors should support the same syntax as
                  backend cursors.
</p>
663 664
      </li><li>Allow PL/RETURN to return row or record functions
<p>                  <a href="http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php">http://archives.postgresql.org/pgsql-patches/2005-11/msg00045.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
665 666 667
</p>
      </li><li>Fix memory leak from exceptions
<p>                  <a href="http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php">http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
668 669 670 671
</p>
      </li><li>Fix problems with RETURN NEXT on tables with
                  dropped/added columns after function creation
<p>                  <a href="http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php">http://archives.postgresql.org/pgsql-patches/2006-02/msg00165.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
672
</p>
673 674 675 676 677 678 679 680 681
    </li></ul>
    </li><li>Other
    <ul>
      <li>Add table function support to pltcl, plpython
      </li><li>Add support for polymorphic arguments and return types to
                  languages other than PL/PgSQL
      </li><li>Add capability to create and call PROCEDURES
      </li><li>Add support for OUT and INOUT parameters to languages other 
                  than PL/PgSQL
Bruce Momjian's avatar
Bruce Momjian committed
682 683
      </li><li>Add PL/Python tracebacks
<p>                  <a href="http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php">http://archives.postgresql.org/pgsql-patches/2006-02/msg00288.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
684
</p>
Bruce Momjian's avatar
Bruce Momjian committed
685
      </li><li>-<em>Allow PL/python to return composite types and result sets</em>
686
    </li></ul>
687 688
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
689
<h1><a name="section_9">Clients</a></h1>
690 691

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
692
  <li>-<em>Have initdb set the input DateStyle (MDY or DMY) based on locale</em>
693 694 695 696 697 698 699
  </li><li>Have pg_ctl look at PGHOST in case it is a socket directory?
  </li><li>Allow pg_ctl to work properly with configuration files located outside
  the PGDATA directory
<p>  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.
700
</p>
701 702 703 704 705 706 707 708
  </li><li>psql
  <ul>
    <li>Have psql show current values for a sequence
    </li><li>Move psql backslash database information into the backend, use
          mnemonic commands? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?psql">psql</a>]
<p>          This would allow non-psql clients to pull the same information out
          of the database as psql.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
709
    </li><li>Fix psql's \d commands more consistent
Bruce Momjian's avatar
Bruce Momjian committed
710
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
711
          <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00014.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
712
</p>
713 714 715
    </li><li>Allow psql \pset boolean variables to set to fixed values, rather
          than toggle
    </li><li>Consistently display privilege information for all objects in psql
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
716
    </li><li>-<em>Improve psql's handling of multi-line statements</em>
717 718
<p>          Currently, while \e saves a single statement as one entry, interactive
          statements are saved one line at a time.  Ideally all statements
Bruce Momjian's avatar
Bruce Momjian committed
719
          would be saved like \e does.
Bruce Momjian's avatar
Bruce Momjian committed
720
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
721
    </li><li>-<em>Allow multi-line column values to align in the proper columns</em>
Bruce Momjian's avatar
Bruce Momjian committed
722 723 724
<p>          If the second output column value is 'a\nb', the 'b' should appear
          in the second display column, rather than the first column as it
          does now.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
725
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
726
    </li><li>-<em>Display IN, INOUT, and OUT parameters in \df</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
727 728 729
    </li><li>Add auto-expanded mode so expanded output is used if the row
          length is wider than the screen width.  
<p>          Consider using auto-expanded mode for backslash commands like \df+.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
730 731 732 733 734 735 736 737
</p>
    </li><li>Prevent tab completion of SET TRANSACTION from querying the
          database and therefore preventing the transaction isolation
          level from being set.
<p>          Currently, SET &lt;tab&gt; 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
738
</p>
739
  </li></ul>
740 741
  </li><li>pg_dump
  <ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
742 743
    <li>-<em>Allow pg_dump to use multiple -t and -n switches, exclusion</em>
           ability, and regular expression object matching
Bruce Momjian's avatar
Bruce Momjian committed
744
    </li><li>%Add dumping of comments on index columns and composite type columns
Bruce Momjian's avatar
Bruce Momjian committed
745
    </li><li>%Add full object name to the tag field.  eg. for operators we need
746
          '=(integer, integer)', instead of just '='.
Bruce Momjian's avatar
Bruce Momjian committed
747
    </li><li>Add pg_dumpall custom format dumps?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
748
    </li><li>-<em>Update pg_dump and psql to use the new COPY libpq API (Christopher)</em>
Bruce Momjian's avatar
Bruce Momjian committed
749 750
    </li><li>Remove unnecessary function pointer abstractions in pg_dump source
          code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
751 752 753 754
    </li><li>Allow selection of individual object(s) of all types, not just
          tables
    </li><li>In a selective dump, allow dumping of an object and all its 
          dependencies
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
755
    </li><li>Add options like pg_restore -l and -L to pg_dump
Bruce Momjian's avatar
Bruce Momjian committed
756
    </li><li>Stop dumping CASCADE on DROP TYPE commands in clean mode
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
757 758
    </li><li>Allow pg_dump --clean to drop roles that own objects or have
          privileges
Bruce Momjian's avatar
Bruce Momjian committed
759
    </li><li>Add -f to pg_dumpall
760
  </li></ul>
761
  </li><li>ecpg
762 763 764 765 766
  <ul>
    <li>Docs
<p>          Document differences between ecpg and the SQL standard and
          information about the Informix-compatibility module.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
767
    </li><li>Solve cardinality &gt; 1 for input descriptors / variables?
768 769 770 771 772
    </li><li>Add a semantic check level, e.g. check if a table really exists
    </li><li>fix handling of DB attributes that are arrays
    </li><li>Use backend PREPARE/EXECUTE facility for ecpg where possible
    </li><li>Implement SQLDA
    </li><li>Fix nested C comments
Bruce Momjian's avatar
Bruce Momjian committed
773
    </li><li>%sqlwarn[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?6">6</a>] should be 'W' if the PRECISION or SCALE value specified
774 775
    </li><li>Make SET CONNECTION thread-aware, non-standard?
    </li><li>Allow multidimensional arrays
Bruce Momjian's avatar
Bruce Momjian committed
776
    </li><li>Add internationalized message strings
Bruce Momjian's avatar
Bruce Momjian committed
777
    </li><li>Implement COPY FROM STDIN
778
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
779 780
  </li><li>libpq
  <ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
781
    <li>-<em>Add a function to support Parse/DescribeStatement capability</em>
Bruce Momjian's avatar
Bruce Momjian committed
782
    </li><li>Add PQescapeIdentifierConn()
Bruce Momjian's avatar
Bruce Momjian committed
783
    </li><li>Prevent PQfnumber() from lowercasing unquoted the column name
784 785 786
<p>          PQfnumber() should never have been doing lowercasing, but 
          historically it has so we need a way to prevent it
</p>
Bruce Momjian's avatar
Bruce Momjian committed
787
    </li><li>Allow statement results to be automatically batched to the client
Bruce Momjian's avatar
Bruce Momjian committed
788
<p>          Currently, all statement results are transferred to the libpq
789 790
          client before libpq makes the results available to the 
          application.  This feature would allow the application to make
Bruce Momjian's avatar
Bruce Momjian committed
791
          use of the first result rows while the rest are transferred, or
792
          held on the server waiting for them to be requested by libpq.
793
          One complexity is that a statement like SELECT 1/col could error
794 795
          out mid-way through the result set.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
796
  </li></ul>
797
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
798
<h1><a name="section_10">Triggers</a></h1>
799
<ul>
Bruce Momjian's avatar
Bruce Momjian committed
800
  <li>Add deferred trigger queue file
801 802 803
<p>  Right now all deferred trigger information is stored in backend
  memory.  This could exhaust memory for very large trigger queues.
  This item involves dumping large queues into files.
Bruce Momjian's avatar
Bruce Momjian committed
804
</p>
805 806 807 808
  </li><li>Allow triggers to be disabled in only the current session.
<p>  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
809
  TRIGGER requires a table lock so it is not ideal for this usage.
810 811 812 813 814 815
</p>
  </li><li>With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
<p>  If the dump is known to be valid, allow foreign keys to be added
  without revalidating the data.
</p>
  </li><li>Allow statement-level triggers to access modified rows
Bruce Momjian's avatar
Bruce Momjian committed
816
  </li><li>Support triggers on columns
817
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00107.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
818
</p>
819 820 821 822 823 824 825
  </li><li>Allow AFTER triggers on system tables
<p>  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.
</p>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
826
<h1><a name="section_11">Dependency Checking</a></h1>
827 828

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
829 830 831
  <li>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
832 833 834
<p>  A more complex solution would be to save multiple plans for different
  cardinality and use the appropriate plan based on the EXECUTE values.
</p>
835
  </li><li>Track dependencies in function bodies and recompile/invalidate
Bruce Momjian's avatar
Bruce Momjian committed
836 837
<p>  This is particularly important for references to temporary tables
  in PL/PgSQL because PL/PgSQL caches query plans.  The only workaround
838 839 840
  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
841
</p>
842
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
843
<h1><a name="section_12">Exotic Features</a></h1>
844 845

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
846
  <li>Add pre-parsing phase that converts non-ISO syntax to supported
847 848 849 850 851 852 853
  syntax
<p>  This could allow SQL written for other databases to run without
  modification.
</p>
  </li><li>Allow plug-in modules to emulate features from other databases
  </li><li>SQL*Net listener that makes PostgreSQL appear as an Oracle database
  to clients
854
  </li><li>Allow statements across databases or servers with transaction
855
  semantics
856
<p>  This can be done using dblink and two-phase commit.
857
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
858 859
  </li><li>Add the features of packages
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
860
    <li>Make private objects accessible only to objects in the same schema
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
861 862 863 864
    </li><li>Allow current_schema.objname to access current schema objects
    </li><li>Add session variables
    </li><li>Allow nested schemas
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
865 866
  </li><li>Consider allowing control of upper/lower case folding of unquoted
  identifiers
867
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php">http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
868
</p>
869
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
870
<h1><a name="section_13">Indexes</a></h1>
871

Bruce Momjian's avatar
Bruce Momjian committed
872 873 874 875 876 877 878 879 880
<ul>
  <li>Allow inherited tables to inherit index, UNIQUE constraint, and primary
  key, foreign key
  </li><li>UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
  inherited table:  INSERT INTO inherit_table (unique_index_col) VALUES
  (dup) should fail
<p>  The main difficulty with this item is the problem of creating an index
  that can span more than one table.
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
881
  </li><li>Allow SELECT ... FOR UPDATE on inherited tables
Bruce Momjian's avatar
Bruce Momjian committed
882 883 884 885 886 887 888 889 890 891
  </li><li>Add UNIQUE capability to non-btree indexes
  </li><li>Prevent index uniqueness checks when UPDATE does not modify the column
<p>  Uniqueness (index) checks are done when updating a column even if the
  column is not modified by the UPDATE.
</p>
  </li><li>Allow the creation of on-disk bitmap indexes which can be quickly
  combined with other bitmap indexes
<p>  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
892
  <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
893 894 895 896 897 898
</p>
  </li><li>Allow use of indexes to search for NULLs
<p>  One solution is to create a partial index on an IS NULL expression.
</p>
  </li><li>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
899
  </li><li>-<em>Add fillfactor to control reserved free space during index creation</em>
Bruce Momjian's avatar
Bruce Momjian committed
900 901 902 903 904 905 906
  </li><li>Allow the creation of indexes with mixed ascending/descending
  specifiers
<p>  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.
</p>
907
  </li><li>Allow constraint_exclusion to work for UNIONs like it does for
908 909
  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
910 911
  </li><li>Allow CREATE INDEX to take an additional parameter for use with
  special index types
Bruce Momjian's avatar
Bruce Momjian committed
912
  </li><li>Consider compressing indexes by storing key values duplicated in
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
913
  several rows as a single index entry
Bruce Momjian's avatar
Bruce Momjian committed
914 915
<p>  This is difficult because it requires datatype-specific knowledge.
</p>
916 917 918 919 920 921
  </li><li>GIST
  <ul>
    <li>Add more GIST index support for geometric data types
    </li><li>Allow GIST indexes to create certain complex index types, like
          digital trees (see Aoki)
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
922 923 924
  </li><li>Hash
  <ul>
    <li>Pack hash index buckets onto disk pages more efficiently
Bruce Momjian's avatar
Bruce Momjian committed
925
<p>          Currently only one hash bucket can be stored on a page. Ideally
Bruce Momjian's avatar
Bruce Momjian committed
926 927 928 929 930 931 932
          several hash buckets could be stored on a single page and greater
          granularity used for the hash algorithm.
</p>
    </li><li>Consider sorting hash buckets so entries can be found using a
          binary search, rather than a linear scan
    </li><li>In hash indexes, consider storing the hash value with or instead
          of the key itself
Bruce Momjian's avatar
Bruce Momjian committed
933 934
    </li><li>Add WAL logging for crash recovery
    </li><li>Allow multi-column hash indexes
Bruce Momjian's avatar
Bruce Momjian committed
935 936
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
937
<h1><a name="section_14">Fsync</a></h1>
938 939 940 941

<ul>
  <li>Improve commit_delay handling to reduce fsync()
  </li><li>Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
Bruce Momjian's avatar
Bruce Momjian committed
942
<p>  Ideally this requires a separate test program that can be run
Bruce Momjian's avatar
Bruce Momjian committed
943 944
  at initdb time or optionally later.  Consider O_SYNC when
  O_DIRECT exists.
Bruce Momjian's avatar
Bruce Momjian committed
945
</p>
Bruce Momjian's avatar
Bruce Momjian committed
946
  </li><li>%Add an option to sync() before fsync()'ing checkpoint files
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
947
  </li><li>Add program to test if fsync has a delay compared to non-fsync
948
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
949
<h1><a name="section_15">Cache Usage</a></h1>
Bruce Momjian's avatar
Bruce Momjian committed
950

951 952 953 954 955 956 957 958 959 960 961 962 963 964 965
<ul>
  <li>Allow free-behind capability for large sequential scans, perhaps using
  posix_fadvise()
<p>  Posix_fadvise() can control both sequential/random file caching and
  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.
</p>
  </li><li>Speed up COUNT(*)
<p>  We could use a fixed row count and a +/- count to follow MVCC
  visibility rules, or a single cached value could be used and
  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
966 967
</p>
  </li><li>Add estimated_count(*) to return an estimate of COUNT(*)
Bruce Momjian's avatar
Bruce Momjian committed
968
<p>  This would use the planner ANALYZE statistics to return an estimated
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
969
  count.
970 971
</p>
  </li><li>Allow data to be pulled directly from indexes
Bruce Momjian's avatar
Bruce Momjian committed
972 973
<p>  Currently indexes do not have enough tuple visibility information 
  to allow data to be pulled from the index without also accessing 
974
  the heap.  One way to allow this is to set a bit on index tuples 
Bruce Momjian's avatar
Bruce Momjian committed
975 976
  to indicate if a tuple is currently visible to all transactions 
  when the first valid heap lookup happens.  This bit would have to 
977 978 979 980 981 982 983 984
  be cleared when a heap tuple is expired.  
</p>
<p>  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.
985
</p>
986
  </li><li>Consider automatic caching of statements at various levels:
987 988 989 990 991 992
  <ul>
    <li>Parsed query tree
    </li><li>Query execute plan
    </li><li>Query results
  </li></ul>
  </li><li>Allow sequential scans to take advantage of other concurrent
Bruce Momjian's avatar
Bruce Momjian committed
993
  sequential scans, also called "Synchronised Scanning"
994 995 996 997
<p>  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
Add:  
Bruce Momjian committed
998 999 1000
</p>
  </li><li>Consider increasing internal areas when shared buffers is increased
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php">http://archives.postgresql.org/pgsql-hackers/2005-10/msg01419.php</a>
1001
</p>
1002
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1003
<h1><a name="section_16">Vacuum</a></h1>
1004 1005 1006

<ul>
  <li>Improve speed with indexes
Bruce Momjian's avatar
Bruce Momjian committed
1007
<p>  For large table adjustments during VACUUM FULL, it is faster to 
Bruce Momjian's avatar
Bruce Momjian committed
1008
  reindex rather than update the index.
1009
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1010 1011
  </li><li>Reduce lock time during VACUUM FULL by moving tuples with read lock,
  then write lock and truncate table
1012 1013 1014
<p>  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
Add:  
Bruce Momjian committed
1015
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1016 1017
  </li><li>Auto-fill the free space map by scanning the buffer cache or by
  checking pages written by the background writer
1018
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php">http://archives.postgresql.org/pgsql-hackers/2006-02/msg01125.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
1019
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php</a>
1020
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1021 1022 1023 1024 1025
  </li><li>Create a bitmap of pages that need vacuuming
<p>  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
1026 1027 1028 1029
  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.
1030
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1031
  </li><li>-<em>Add system view to show free space map contents</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1032 1033
  </li><li>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
1034 1035
  </li><li>Allow FSM page return free space based on table clustering, to assist
  in maintaining clustering?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1036 1037
  </li><li>Consider shrinking expired tuples to just their headers
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php">http://archives.postgresql.org/pgsql-patches/2006-03/msg00142.php</a>
1038
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1039 1040 1041 1042 1043 1044
  </li><li>Allow heap reuse of UPDATEd rows if no indexed columns are changed,
  and old and new versions are on the same heap page?
<p>  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.
1045
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01305.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
1046
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php">http://archives.postgresql.org/pgsql-hackers/2006-06/msg01534.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1047
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1048 1049
  </li><li>Reuse index tuples that point to heap tuples that are not visible to 
  anyone?
1050 1051
  </li><li>Auto-vacuum
  <ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1052
    <li>Use free-space map information to guide refilling
Bruce Momjian's avatar
Bruce Momjian committed
1053 1054
    </li><li>%Issue log message to suggest VACUUM FULL if a table is nearly
          empty?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1055 1056
    </li><li>Improve xid wraparound detection by recording per-table rather
          than per-database
Bruce Momjian's avatar
Bruce Momjian committed
1057
    </li><li>Consider logging activity either to the logs or a system view
Bruce Momjian's avatar
Bruce Momjian committed
1058
    </li><li>Turn on by default
1059 1060
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01852.php</a>
</p>
1061 1062
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1063
<h1><a name="section_17">Locking</a></h1>
1064 1065

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
1066
  <li>Fix priority ordering of read and write light-weight locks (Neil)
1067
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1068
<h1><a name="section_18">Startup Time Improvements</a></h1>
1069 1070

<ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1071
  <li>Experiment with multi-threaded backend for backend creation [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>]
1072 1073
<p>  This would prevent the overhead associated with process creation. Most
  operating systems have trivial process creation time compared to
Bruce Momjian's avatar
Bruce Momjian committed
1074
  database startup overhead, but a few operating systems (Win32,
Bruce Momjian's avatar
Bruce Momjian committed
1075
  Solaris) might benefit from threading.  Also explore the idea of
1076
  a single session using multiple threads to execute a statement faster.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1077 1078 1079
</p>
  </li><li>Experiment with multi-threaded backend better resource utilization
<p>  This would allow a single query to make use of multiple CPU's or
Bruce Momjian's avatar
Bruce Momjian committed
1080 1081 1082 1083
  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.
1084 1085 1086 1087 1088 1089 1090
</p>
  </li><li>Add connection pooling
<p>  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.
</p>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1091
<h1><a name="section_19">Write-Ahead Log</a></h1>
1092 1093 1094

<ul>
  <li>Eliminate need to write full pages to WAL before page modification [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wal">wal</a>]
Bruce Momjian's avatar
Bruce Momjian committed
1095
<p>  Currently, to protect against partial disk page writes, we write
1096 1097 1098 1099
  full page images to WAL before they are modified so we can correct any
  partial page writes during recovery.  These pages can also be
  eliminated from point-in-time archive files.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1100
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
1101
    <li>When off, write CRC to WAL and check file system blocks
Bruce Momjian's avatar
Bruce Momjian committed
1102
           on recovery
Bruce Momjian's avatar
Bruce Momjian committed
1103 1104 1105
<p>           If CRC check fails during recovery, remember the page in case
           a later CRC for that page properly matches.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1106 1107 1108
    </li><li>Write full pages during file system write and not when
           the page is modified in the buffer cache
<p>           This allows most full page writes to happen in the background
Bruce Momjian's avatar
Bruce Momjian committed
1109 1110 1111
           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
1112 1113
</p>
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1114
  </li><li>Allow WAL traffic to be streamed to another server for stand-by
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1115
  replication
1116
  </li><li>Reduce WAL traffic so only modified values are written rather than
Bruce Momjian's avatar
Bruce Momjian committed
1117
  entire rows?
1118 1119
  </li><li>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
1120
  </li><li>Allow WAL information to recover corrupted pg_controldata
1121
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php</a>
1122
</p>
1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135
  </li><li>Find a way to reduce rotational delay when repeatedly writing
  last WAL page
<p>  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.
</p>
  </li><li>Allow buffered WAL writes and fsync
<p>  Instead of guaranteeing recovery of all committed transactions, this
  would provide improved performance by delaying WAL writes and fsync
  so an abrupt operating system restart might lose a few seconds of
  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
Add:  
Bruce Momjian committed
1136
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1137 1138
  </li><li>Allow WAL logging to be turned off for a table, but the table
  might be dropped or truncated during crash recovery [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1139
<p>  Allow tables to bypass WAL writes and just fsync() dirty pages on
Bruce Momjian's avatar
Bruce Momjian committed
1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152
  commit.  This should be implemented using ALTER TABLE, e.g. ALTER 
  TABLE PERSISTENCE [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo? DROP | TRUNCATE | DEFAULT "> DROP | TRUNCATE | DEFAULT </a>].  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.
</p>
  </li><li>Allow WAL logging to be turned off for a table, but the table would
  avoid being truncated/dropped [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
<p>  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.
1153 1154
</p>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1155
<h1><a name="section_20">Optimizer / Executor</a></h1>
1156 1157

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
1158
  <li>Improve selectivity functions for geometric operators
Bruce Momjian's avatar
Bruce Momjian committed
1159
  </li><li>Allow ORDER BY ... LIMIT # to select high/low value without sort or
1160
  index using a sequential scan for highest/lowest values
Bruce Momjian's avatar
Bruce Momjian committed
1161
<p>  Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
1162 1163
  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
1164
  MIN/MAX already does this, but not for LIMIT &gt; 1.
1165
</p>
1166 1167 1168 1169 1170
  </li><li>Precompile SQL functions to avoid overhead
  </li><li>Create utility to compute accurate random_page_cost value
  </li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
  </li><li>Have EXPLAIN ANALYZE highlight poor optimizer estimates
  </li><li>Consider using hash buckets to do DISTINCT, rather than sorting
Bruce Momjian's avatar
Bruce Momjian committed
1171 1172
<p>  This would be beneficial when there are few distinct values.  This is
  already used by GROUP BY.
1173
</p>
1174
  </li><li>Log statements where the optimizer row estimates were dramatically
Bruce Momjian's avatar
Bruce Momjian committed
1175
  different from the number of rows actually found?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1176 1177 1178
  </li><li>Consider compressed annealing to search for query plans
<p>  This might replace GEQO, <a href="http://sixdemonbag.org/Djinni">http://sixdemonbag.org/Djinni</a>.
</p>
1179
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1180
<h1><a name="section_21">Miscellaneous Performance</a></h1>
1181 1182 1183 1184 1185 1186

<ul>
  <li>Do async I/O for faster random read-ahead of data
<p>  Async I/O allows multiple I/O requests to be sent to the disk with
  results coming back asynchronously.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1187
  </li><li>Use mmap() rather than SYSV shared memory or to write WAL files?
1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200
<p>  This would remove the requirement for SYSV SHM but would introduce
  portability issues. Anonymous mmap (or mmap to /dev/zero) is required
  to prevent I/O overhead.
</p>
  </li><li>Consider mmap()'ing files into a backend?
<p>  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,
  leading to thousands of mappings.  Another problem is that there is no
  way to _prevent_ I/O to disk from the dirty shared buffers so changes
  could hit disk before WAL is written.
</p>
  </li><li>Add a script to ask system configuration questions and tune postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
1201 1202 1203 1204 1205 1206 1207 1208
  </li><li>Merge xmin/xmax/cmin/cmax back into three header fields
<p>  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
1209
  could only see rows from another completed transaction. However,
Bruce Momjian's avatar
Bruce Momjian committed
1210 1211 1212 1213 1214
  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
1215
  proper visibility of the row's cmin, for example, for cursors.
Bruce Momjian's avatar
Bruce Momjian committed
1216 1217
</p>
<p>  One possible solution is to create a phantom cid which represents a
Bruce Momjian's avatar
Bruce Momjian committed
1218 1219
  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
1220
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1221 1222
  </li><li>Consider ways of storing rows more compactly on disk
  <ul>
1223 1224 1225 1226 1227 1228 1229
    <li>Support a smaller header for short variable-length fields?
<p>          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.
          <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
1230
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1231 1232
    </li><li>Reduce the row header size?
  </li></ul>
1233
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1234
<h1><a name="section_22">Source Code</a></h1>
1235 1236 1237 1238 1239

<ul>
  <li>Add use of 'const' for variables in source tree
  </li><li>Move some things from /contrib into main tree
  </li><li>Move some /contrib modules out to their own project sites
1240 1241 1242
<p>  Particularly, move GPL-licensed /contrib/userlock and 
  /contrib/dbmirror/clean_pending.pl.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1243
  </li><li>%Remove warnings created by -Wcast-align
1244 1245 1246 1247
  </li><li>Move platform-specific ps status display info from ps_status.c to ports
  </li><li>Add optional CRC checksum to heap and index pages
  </li><li>Improve documentation to build only interfaces (Marc)
  </li><li>Remove or relicense modules that are not under the BSD license, if possible
Bruce Momjian's avatar
Bruce Momjian committed
1248
  </li><li>%Remove memory/file descriptor freeing before ereport(ERROR)
1249
  </li><li>Acquire lock on a relation before building a relcache entry for it
Bruce Momjian's avatar
Bruce Momjian committed
1250 1251
  </li><li>%Promote debug_query_string into a server-side function current_query()
  </li><li>%Allow the identifier length to be increased via a configure option
1252
  </li><li>Allow cross-compiling by generating the zic database on the target system
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1253
  </li><li>Improve NLS maintenance of libpgport messages linked onto applications
1254 1255 1256 1257 1258 1259
  </li><li>Allow ecpg to work with MSVC and BCC
  </li><li>Add xpath_array() to /contrib/xml2 to return results as an array
  </li><li>Allow building in directories containing spaces
<p>  This is probably not possible because 'gmake' and other compiler tools
  do not fully support quoting of paths with spaces.
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1260
  </li><li>-<em>Allow installing to directories containing spaces</em>
1261 1262 1263 1264 1265
<p>  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.
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1266
  </li><li>Fix sgmltools so PDFs can be generated with bookmarks
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1267
  </li><li>-*%Clean up compiler warnings (especially with gcc version 4)*
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1268 1269
  </li><li>Use UTF8 encoding for NLS messages so all server encodings can
  read them properly
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1270
  </li><li>Update Bonjour to work with newer cross-platform SDK
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1271
  </li><li>-<em>Remove BeOS and QNX-specific code</em>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1272 1273
  </li><li>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
1274 1275 1276
  </li><li>Improve port/qsort() to handle sorts with 50% unique and 50% duplicate
  value [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?qsort">qsort</a>]
<p>  This involves choosing better pivot points for the quicksort.
Bruce Momjian's avatar
Bruce Momjian committed
1277
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1278
  </li><li>Consider detoasting keys before sorting
Bruce Momjian's avatar
Bruce Momjian committed
1279
  </li><li>Consider GnuTLS if OpenSSL license becomes a problem
1280
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php">http://archives.postgresql.org/pgsql-patches/2006-05/msg00040.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1281
</p>
1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293
  </li><li>Win32
  <ul>
    <li>Remove configure.in check for link failure when cause is found
    </li><li>Remove readdir() errno patch when runtime/mingwex/dirent.c rev
          1.4 is released
    </li><li>Remove psql newline patch when we find out why mingw outputs an
          extra newline
    </li><li>Allow psql to use readline once non-US code pages work with
          backslashes
    </li><li>Re-enable timezone output on log_line_prefix '%t' when a
          shorter timezone string is available
    </li><li>Fix problem with shared memory on the Win32 Terminal Server
1294 1295 1296
    </li><li>Improve signal handling
<p>          <a href="http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php">http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php</a>
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1297 1298 1299
    </li><li>Add long file support for binary pg_dump output
<p>          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
1300 1301 1302
          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
Add:  
Bruce Momjian committed
1303
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1304
    </li><li>-<em>Port contrib/xml2</em>
Bruce Momjian's avatar
Bruce Momjian committed
1305
    </li><li>Check WSACancelBlockingCall() for interrupts [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?win32intr">win32intr</a>]
1306 1307 1308 1309 1310 1311 1312
  </li></ul>
  </li><li>Wire Protocol Changes
  <ul>
    <li>Allow dynamic character set handling
    </li><li>Add decoded type, length, precision
    </li><li>Use compression?
    </li><li>Update clients to use data types, typmod, <a href="http://schema.table.column">schema.table.column</a>/ names
1313
          of result sets using new statement protocol
1314 1315
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1316
<h1><a name="section_23">Features We Do _Not_ Want</a></h1>
1317 1318

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
1319
  <li>All backends running as threads in a single process (not wanted)
1320 1321 1322 1323
<p>  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.
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1324
  </li><li>Optimizer hints (not wanted)
1325 1326 1327
<p>  Optimizer hints are used to work around problems in the optimizer.  We
  would rather have the problems reported and fixed.
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00506.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
1328 1329 1330 1331 1332
</p>
  </li><li>Allow AS in "SELECT col AS label" to be optional (not wanted)
<p>  Because we support postfix operators, it isn't possible to make AS
  optional and continue to use bison.
  <a href="http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php">http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php</a>
1333 1334
</p>
</li></ul>
1335 1336
<hr/>

Bruce Momjian's avatar
Bruce Momjian committed
1337
<h2><a name="section_23_1">Developers who have claimed items are:</a></h2>
1338 1339 1340
<ul>
  <li>Alvaro is Alvaro Herrera &lt;<a href="mailto:alvherre@dcc.uchile.cl">alvherre@dcc.uchile.cl</a>&gt;
  </li><li>Andrew is Andrew Dunstan &lt;<a href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>&gt;
Bruce Momjian's avatar
Bruce Momjian committed
1341
  </li><li>Bruce is Bruce Momjian &lt;<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>&gt; of EnterpriseDB
1342 1343 1344
  </li><li>Christopher is Christopher Kings-Lynne &lt;<a href="mailto:chriskl@familyhealth.com.au">chriskl@familyhealth.com.au</a>&gt; of
    Family Health Network
  </li><li>D'Arcy is D'Arcy J.M. Cain &lt;<a href="mailto:darcy@druid.net">darcy@druid.net</a>&gt; of The Cain Gang Ltd.
Bruce Momjian's avatar
Bruce Momjian committed
1345
  </li><li>David is David Fetter &lt;<a href="mailto:david@fetter.org">david@fetter.org</a>&gt;
1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357
  </li><li>Fabien is Fabien Coelho &lt;<a href="mailto:coelho@cri.ensmp.fr">coelho@cri.ensmp.fr</a>&gt;
  </li><li>Gavin is Gavin Sherry &lt;<a href="mailto:swm@linuxworld.com.au">swm@linuxworld.com.au</a>&gt; of Alcove Systems Engineering
  </li><li>Greg is Greg Sabino Mullane &lt;<a href="mailto:greg@turnstep.com">greg@turnstep.com</a>&gt;
  </li><li>Jan is Jan Wieck &lt;<a href="mailto:JanWieck@Yahoo.com">JanWieck@Yahoo.com</a>&gt; of Afilias, Inc.
  </li><li>Joe is Joe Conway &lt;<a href="mailto:mail@joeconway.com">mail@joeconway.com</a>&gt;
  </li><li>Karel is Karel Zak &lt;<a href="mailto:zakkr@zf.jcu.cz">zakkr@zf.jcu.cz</a>&gt;
  </li><li>Magnus is Magnus Hagander &lt;<a href="mailto:mha@sollentuna.net">mha@sollentuna.net</a>&gt;
  </li><li>Marc is Marc Fournier &lt;<a href="mailto:scrappy@hub.org">scrappy@hub.org</a>&gt; of PostgreSQL, Inc.
  </li><li>Matthew T. O'Connor &lt;<a href="mailto:matthew@zeut.net">matthew@zeut.net</a>&gt;
  </li><li>Michael is Michael Meskes &lt;<a href="mailto:meskes@postgresql.org">meskes@postgresql.org</a>&gt; of Credativ
  </li><li>Neil is Neil Conway &lt;<a href="mailto:neilc@samurai.com">neilc@samurai.com</a>&gt;
  </li><li>Oleg is Oleg Bartunov &lt;<a href="mailto:oleg@sai.msu.su">oleg@sai.msu.su</a>&gt;
Bruce Momjian's avatar
Bruce Momjian committed
1358
  </li><li>Pavel is Pavel Stehule &lt;<a href="mailto:pavel.stehule@hotmail.com">pavel.stehule@hotmail.com</a>&gt;
1359 1360 1361 1362 1363
  </li><li>Peter is Peter Eisentraut &lt;<a href="mailto:peter_e@gmx.net">peter_e@gmx.net</a>&gt;
  </li><li>Philip is Philip Warner &lt;<a href="mailto:pjw@rhyme.com.au">pjw@rhyme.com.au</a>&gt; of Albatross Consulting Pty. Ltd.
  </li><li>Rod is Rod Taylor &lt;<a href="mailto:pg@rbt.ca">pg@rbt.ca</a>&gt;
  </li><li>Simon is Simon Riggs &lt;<a href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>&gt;
  </li><li>Stephan is Stephan Szabo &lt;<a href="mailto:sszabo@megazone23.bigpanda.com">sszabo@megazone23.bigpanda.com</a>&gt;
Bruce Momjian's avatar
Bruce Momjian committed
1364
  </li><li>Tatsuo is Tatsuo Ishii &lt;<a href="mailto:ishii@sraoss.co.jp">ishii@sraoss.co.jp</a>&gt; of SRA OSS, Inc. Japan
Bruce Momjian's avatar
Bruce Momjian committed
1365
  </li><li>Teodor is Teodor Sigaev &lt;<a href="mailto:teodor@sigaev.ru">teodor@sigaev.ru</a>&gt;
1366 1367
  </li><li>Tom is Tom Lane &lt;<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>&gt; of Red Hat
</li></ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1368

1369 1370
</body>
</html>