TODO.html 73.3 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/>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
11
Last updated:           Sat Feb  3 20:50:56 EST 2007
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>
16
<p><strong>A hyphen, "-", marks changes that will appear in the upcoming 8.3 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
</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/>
Bruce Momjian's avatar
Bruce Momjian committed
23 24
first.  There is also a developer's wiki at<br/>
<a href="http://developer.postgresql.org">http://developer.postgresql.org</a>.
25
</p>
Bruce Momjian's avatar
Bruce Momjian committed
26
<h1><a name="section_2">Administration</a></h1>
27 28

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
29
  <li>Allow major upgrades without dump/reload, perhaps using pg_upgrade 
Bruce Momjian's avatar
Bruce Momjian committed
30
  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pg_upgrade">pg_upgrade</a>]
Bruce Momjian's avatar
Bruce Momjian committed
31
  </li><li>Check for unreferenced table files created by transactions that were
32
  in-progress when the server terminated abruptly
Bruce Momjian's avatar
Bruce Momjian committed
33 34
<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
35 36
  </li><li>Allow administrators to safely terminate individual sessions either
  via an SQL function or SIGTERM 
Bruce Momjian's avatar
Bruce Momjian committed
37 38 39 40
<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.
41
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg00174.php</a>
42
</p>
Bruce Momjian's avatar
Bruce Momjian committed
43
  </li><li>%Set proper permissions on non-system schemas during db creation
44 45 46
<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
47 48 49
  </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
50
  </li><li>Add function to report the time of the most recent server reload
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
51 52 53
  </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
54 55 56
  </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.
57 58
  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
59
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
60 61 62 63 64 65 66
  </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
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
67 68 69 70 71 72
  </li><li>Allow more complex user/database default GUC settings
<p>  Currently, ALTER USER and ALTER DATABASE support per-user and
  per-database defaults.  Consider adding per-user-and-database
  defaults so things like search_path can be defaulted for a 
  specific user connecting to a specific database.
</p>
73 74 75 76 77 78 79 80 81
  </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
82 83
  </li><li>Configuration files
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
84
    <li>Allow commenting of variables in postgresql.conf to restore them
Bruce Momjian's avatar
Bruce Momjian committed
85
          to defaults
Bruce Momjian's avatar
Bruce Momjian committed
86 87
<p>          Currently, if a variable is commented out, it keeps the
          previous uncommented value until a server restarted.
88
          <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01481.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01481.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
89 90 91 92 93 94 95 96
</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
97
</p>
Bruce Momjian's avatar
Bruce Momjian committed
98
    </li><li>%Allow postgresql.conf file values to be changed via an SQL
Bruce Momjian's avatar
Bruce Momjian committed
99
          API, perhaps using SET GLOBAL
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
100
    </li><li>Allow the server to be stopped/restarted via an SQL API
Bruce Momjian's avatar
Bruce Momjian committed
101
    </li><li>Issue a warning if a change-on-restart-only postgresql.conf value
Bruce Momjian's avatar
Bruce Momjian committed
102
          is modified  and the server config files are reloaded
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
103
    </li><li>Mark change-on-restart-only values in postgresql.conf
Bruce Momjian's avatar
Bruce Momjian committed
104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125
  </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
Done:  
Bruce Momjian committed
126
    </li><li>-<em>Add a GUC variable to control the tablespace for temporary objects</em>
Bruce Momjian's avatar
Bruce Momjian committed
127 128 129 130
          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
131
    </li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
Bruce Momjian's avatar
Bruce Momjian committed
132
          structure on the recovery computer is different from the original
Bruce Momjian's avatar
Bruce Momjian committed
133
    </li><li>Allow per-tablespace quotas
Bruce Momjian's avatar
Bruce Momjian committed
134
  </li></ul>
135
  </li><li>Point-In-Time Recovery (PITR)
Bruce Momjian's avatar
Bruce Momjian committed
136
  <ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
137
    <li>Allow a warm standby system to also allow read-only statements
Bruce Momjian's avatar
Bruce Momjian committed
138 139 140
            [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p>            This is useful for checking PITR recovery.
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
141 142
    </li><li>%Create dump tool for write-ahead logs for use in determining
            transaction id for point-in-time recovery
Bruce Momjian's avatar
Bruce Momjian committed
143
    </li><li>Allow the PITR process to be debugged and data examined
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
144 145 146 147
    </li><li>Allow recovery.conf to allow the same syntax as
            postgresql.conf, including quoting
<p>            <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php</a>
</p>
Bruce Momjian's avatar
Bruce Momjian committed
148 149
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
150
<h1><a name="section_3">Monitoring</a></h1>
Bruce Momjian's avatar
Bruce Momjian committed
151 152 153 154 155 156

<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
Done:  
Bruce Momjian committed
157
  </li><li>-<em>Add ability to monitor the use of temporary sort files</em>
158
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
159
<h1><a name="section_4">Data Types</a></h1>
160 161

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
162 163 164
  <li>-<em>Make 64-bit version of the MONEY data type</em>
  </li><li>Add locale-aware MONEY type, and support multiple currencies
<p>  <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
165
</p>
166
  </li><li>Change NUMERIC to enforce the maximum precision
Bruce Momjian's avatar
Bruce Momjian committed
167
  </li><li>Add NUMERIC division operator that doesn't round?
168
<p>  Currently NUMERIC <u>rounds</u> the result to the specified precision.  
Bruce Momjian's avatar
Bruce Momjian committed
169 170 171 172 173 174 175 176 177 178
  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>
179
  <li>Fix data types where equality comparison isn't intuitive, e.g. box
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
180 181
  </li><li>Allow user-defined types to specify a type modifier at table creation
  time
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
182
  </li><li>-<em>Allow user-defined types to accept 'typmod' parameters</em>
Bruce Momjian's avatar
Bruce Momjian committed
183 184
<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
185
  <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
186 187 188
</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
189 190 191
</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
192
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01681.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
193
</p>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
194
  </li><li>-<em>Add Globally/Universally Unique Identifier (GUID/UUID)</em>
Bruce Momjian's avatar
Bruce Momjian committed
195
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php">http://archives.postgresql.org/pgsql-patches/2006-09/msg00209.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
196
  <a href="http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php">http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
197
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
198 199
  </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
200 201 202
</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
203 204 205
</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
206
</p>
207
  </li><li>Dates and Times
208
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
209
    <li>Allow infinite dates and intervals just like infinite timestamps
210 211 212 213 214
    </li><li>Merge hardwired timezone names with the TZ database; allow either 
          kind everywhere a TZ name is currently taken
    </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
215
          computations should adjust based on the time zone rules.
216
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
217
    </li><li>Fix SELECT '0.01 years'::interval, '0.01 months'::interval
Bruce Momjian's avatar
Bruce Momjian committed
218 219 220 221 222 223 224 225 226 227 228 229
    </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    
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
230 231 232 233
    </li><li>Extend timezone code to allow 64-bit values so we can
          represent years beyond 2038
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php</a>
</p>
234
    </li><li>Add ISO INTERVAL handling
235 236
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
237 238
<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>
239 240
</p>
<ul>
Bruce Momjian's avatar
Bruce Momjian committed
241
  <li>Support ISO INTERVAL syntax if units cannot be determined from
242
                  the string, and are supplied after the string
Bruce Momjian's avatar
Bruce Momjian committed
243 244 245 246 247
<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'.
248 249 250
</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
251 252 253 254 255 256 257 258 259 260
                  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.
261
</p>
262 263
  </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
264
                  INTERVAL MONTH), and this should return '12 months'
265
  </li><li>Round or truncate values to the requested precision, e.g.
266
                  INTERVAL '11 months' AS YEAR should return one or zero
267
  </li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
268
  <ul>
269 270
    <li>Arrays
    <ul>
Bruce Momjian's avatar
Bruce Momjian committed
271
      <li>Delay resolution of array expression's data type so assignment
272
          coercion can be performed on empty array expressions
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
273 274
      </li><li>Add support for arrays of domains
      </li><li>Add support for arrays of complex types
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
275 276
      </li><li>ARRAY[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?[1,2">[1,2</a>],[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?3,4">3,4</a>]])[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?1">1</a>] should return the same values as
          ARRAY[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?[1,2">[1,2</a>],[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?3,4">3,4</a>]])[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?1:1">1:1</a>];
277 278 279 280 281 282
    </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
283 284
<p>          /contrib/lo offers this functionality.
</p>
285
      </li><li>Allow read/write into TOAST values like large objects
286
<p>          This requires the TOAST column to be stored EXTERNAL.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
287
</p>
288
      </li><li>Add API for 64-bit large object access
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
289
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php">http://archives.postgresql.org/pgsql-hackers/2005-09/msg00781.php</a>
290
</p>
291
    </li></ul>
292 293
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
294
<h1><a name="section_5">Functions</a></h1>
Bruce Momjian's avatar
Bruce Momjian committed
295 296

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
297
  <li>Allow INET subnet tests using non-constants to be indexed
Bruce Momjian's avatar
Bruce Momjian committed
298
  </li><li>%Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Bruce Momjian's avatar
Bruce Momjian committed
299
  pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
300 301
<p>  These would be for application use, not for use by pg_dump.
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
302
  </li><li>Allow to_date() and to_timestamp() accept localized month names
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
303 304 305 306 307 308
  </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
309 310 311 312 313 314 315 316 317 318 319 320 321 322
  </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
Add:  
Bruce Momjian committed
323
  </li><li>Add ISO day of week format 'ID' to to_char() where Monday = 1
Bruce Momjian's avatar
Bruce Momjian committed
324
  </li><li>Add a field 'isoyear' to extract(), based on the ISO week
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
325
  </li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
326
  </li><li>Implement inlining of set-returning functions defined in SQL
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
327
  </li><li>Allow SQL-language functions to return results from RETURNING queries
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
328 329 330
  </li><li>Enforce typmod for function inputs, function results and parameters for
  spi_prepare'd statements called from PLs
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01403.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
331 332
</p>
  </li><li>Tighten function permission checks
333
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00568.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
334
</p>
Bruce Momjian's avatar
Bruce Momjian committed
335
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
336
<h1><a name="section_6">Multi-Language Support</a></h1>
337 338 339 340

<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
341 342 343 344
<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.
345
</p>
Bruce Momjian's avatar
Bruce Momjian committed
346
  </li><li>Allow encoding on a per-column basis optionally using the ICU library:
347
<p>  Right now only one encoding is allowed per database.  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?locale">locale</a>]
348
  <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
349 350
  <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
351
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg00662.php</a>
352
</p>
353
  </li><li>Add CREATE COLLATE?  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?locale">locale</a>]
354
  </li><li>Support multiple simultaneous character sets, per SQL92
Bruce Momjian's avatar
Bruce Momjian committed
355
  </li><li>Improve UTF8 combined character handling?
356 357
  </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
358
  </li><li>Fix problems with wrong runtime encoding conversion for NLS message files
Bruce Momjian's avatar
Bruce Momjian committed
359 360
  </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
361 362 363 364
</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>
365
  <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
366 367 368 369
</p>
  </li><li>Set client encoding based on the client operating system encoding
<p>  Currently client_encoding is set in postgresql.conf, which
  defaults to the server encoding.
370
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php">http://archives.postgresql.org/pgsql-hackers/2006-08/msg01696.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
371
</p>
372
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
373
<h1><a name="section_7">Views / Rules</a></h1>
374 375

<ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
376
  <li>Automatically create rules on views so they are updateable, per SQL99
377
<p>  We can only auto-create rules for simple views.  For more complex
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
378
  cases users will still have to write rules manually.
Bruce Momjian's avatar
Bruce Momjian committed
379
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00586.php</a>
380 381 382
</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
383
  </li><li>Allow VIEW/RULE recompilation when the underlying tables change
Bruce Momjian's avatar
Bruce Momjian committed
384 385 386 387
<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>
388
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
389
<h1><a name="section_8">SQL Commands</a></h1>
390 391

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
392
  <li>Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
393
  </li><li>Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
Bruce Momjian's avatar
Bruce Momjian committed
394 395
  </li><li>%Allow SET CONSTRAINTS to be qualified by schema/table name
  </li><li>%Add a separate TRUNCATE permission
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
396 397 398
<p>  Currently only the owner can TRUNCATE a table because triggers are not
  called, and the table is locked in exclusive mode.
</p>
399 400 401 402 403 404 405 406
  </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
407 408
  </li><li>Invalidate prepared queries, like INSERT, when the table definition
  is altered
409 410 411 412 413 414 415 416
  </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
417
</p>
418
  </li><li>Add a GUC variable to warn about non-standard SQL usage in queries
419
  </li><li>Add SQL-standard MERGE command, typically used to merge two tables
Bruce Momjian's avatar
Bruce Momjian committed
420
  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
421 422 423 424 425
<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
426
  [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
Bruce Momjian's avatar
Bruce Momjian committed
427
<p>  To implement this cleanly requires that the table have a unique index
428 429 430
  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
431
</p>
432 433
  </li><li>Add NOVICE output level for helpful messages like automatic sequence/index
  creation
434
  </li><li>Add RESET CONNECTION command to reset all session state
435
<p>  This would include resetting of all variables (RESET ALL), dropping of
436 437 438 439
  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
440 441
  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 
442
  notify the protocol when a RESET CONNECTION command is used.
Bruce Momjian's avatar
Bruce Momjian committed
443
  <a href="http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php">http://archives.postgresql.org/pgsql-patches/2006-04/msg00192.php</a>
444
</p>
445
  </li><li>Add GUC to issue notice about statements that use unjoined tables
446
  </li><li>Allow EXPLAIN to identify tables that were skipped because of 
447
  constraint_exclusion
448
  </li><li>Allow EXPLAIN output to be more easily processed by scripts
Bruce Momjian's avatar
Bruce Momjian committed
449
  </li><li>Enable standard_conforming_strings
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
450 451 452 453 454 455 456
  </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
457
  </li><li>Simplify dropping roles that have objects in several databases
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
458
  </li><li>Allow COMMENT ON to accept an expression rather than just a string
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
459 460
  </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
Bruce Momjian committed
461
  </li><li>Add SQL99 WITH clause to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
462
  </li><li>Add SQL:2003 WITH RECURSIVE (hierarchical) queries to SELECT
Bruce Momjian's avatar
Bruce Momjian committed
463 464 465 466
  </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
Bruce Momjian committed
467
  </li><li>Allow DISTINCT to work in multiple-argument aggregate calls
Bruce Momjian's avatar
Bruce Momjian committed
468 469
  </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
470
  </li><li>Implement SQL:2003 window functions
471 472 473 474 475 476
  </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
Add:  
Bruce Momjian committed
477 478 479 480
    </li><li>Fix transaction restriction checks for CREATE DATABASE and
          other commands
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php</a>
</p>
481 482 483
  </li></ul>
  </li><li>UPDATE
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
484
    <li>Allow UPDATE tab SET ROW (col, ...) = (SELECT...)
Bruce Momjian's avatar
Bruce Momjian committed
485
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php">http://archives.postgresql.org/pgsql-hackers/2006-07/msg01306.php</a>
486
</p>
487
  </li></ul>
488 489
  </li><li>ALTER
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
490
    <li>%Have ALTER TABLE RENAME rename SERIAL sequence names
Bruce Momjian's avatar
Bruce Momjian committed
491
    </li><li>Add ALTER DOMAIN to modify the underlying data type
Bruce Momjian's avatar
Bruce Momjian committed
492
    </li><li>%Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
493
<p>          <a href="http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php">http://archives.postgresql.org/pgsql-patches/2006-02/msg00168.php</a>
494
</p>
Bruce Momjian's avatar
Bruce Momjian committed
495
    </li><li>%Allow ALTER TABLE to change constraint deferrability and actions
Bruce Momjian's avatar
Bruce Momjian committed
496
    </li><li>Add missing object types for ALTER ... SET SCHEMA
497
    </li><li>Allow ALTER TABLESPACE to move to different directories
498
    </li><li>Allow databases to be moved to different tablespaces
499 500
    </li><li>Allow moving system tables to other tablespaces, where possible
<p>          Currently non-global system tables must be in the default database
501
          tablespace. Global system tables can never be moved.
502
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
503
    </li><li>Prevent parent tables from altering or dropping constraints
504 505 506 507
          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
Add:  
Bruce Momjian committed
508
    </li><li>Have ALTER INDEX update the name of a constraint using that index
Bruce Momjian's avatar
Bruce Momjian committed
509
    </li><li>Add ALTER TABLE RENAME CONSTRAINT, update index name also
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
510 511 512 513
    </li><li>Allow column display reordering by recording a display,
          storage, and permanent id for every column?
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00782.php</a>
</p>
514 515 516
  </li></ul>
  </li><li>CLUSTER
  <ul>
517 518
    <li>Make CLUSTER preserve recently-dead tuples per MVCC requirements
    </li><li>Automatically maintain clustering on a table
519 520
<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
521
          partially filled for easier reorganization.  Another idea would
522 523 524 525
          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
526
          <a href="http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php">http://archives.postgresql.org/pgsql-performance/2004-08/msg00349.php</a>
527
</p>
Bruce Momjian's avatar
Bruce Momjian committed
528
    </li><li>%Add default clustering to system tables
529 530 531 532 533 534 535 536 537 538
<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
Bruce Momjian committed
539 540
    </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
541
          be removed or have its heap and index files truncated.  One
Bruce Momjian's avatar
Bruce Momjian committed
542 543 544
          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
545
</p>
546
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
547 548 549
  </li><li>GRANT/REVOKE
  <ul>
    <li>Allow column-level privileges
Bruce Momjian's avatar
Bruce Momjian committed
550
    </li><li>%Allow GRANT/REVOKE permissions to be applied to all schema objects
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
551
          with one command
Bruce Momjian's avatar
Bruce Momjian committed
552 553 554 555
<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
556
    </li><li>Allow GRANT/REVOKE permissions to be inherited by objects based on
Bruce Momjian's avatar
Bruce Momjian committed
557
          schema permissions
Bruce Momjian's avatar
Bruce Momjian committed
558
    </li><li>Allow SERIAL sequences to inherit permissions from the base table?
Bruce Momjian's avatar
Bruce Momjian committed
559
  </li></ul>
560 561 562 563 564 565 566 567 568
  </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
569
          cursor?
570 571 572 573
  </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
574
    </li><li>In rules, allow VALUES() to contain a mixture of 'old' and 'new'
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
575
          references
576
  </li></ul>
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
577
  </li><li>SHOW/SET
578
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
579
    <li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
580
          ANALYZE, and CLUSTER
Bruce Momjian's avatar
Bruce Momjian committed
581
    </li><li>Add SET PATH for schemas?
582 583 584
<p>          This is basically the same as SET search_path.
</p>
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
585 586 587 588 589 590
  </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
591 592 593 594
    </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>
595 596 597 598 599 600
</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
601
          <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>
602
          <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
603
</p>
Bruce Momjian's avatar
Bruce Momjian committed
604
  </li></ul>
605
  </li><li>Server-Side Languages
606
  <ul>
607 608 609
    <li>PL/pgSQL
    <ul>
      <li>Fix RENAME to work on variables other than OLD/NEW
Bruce Momjian's avatar
Bruce Momjian committed
610
<p>                  <a href="http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php">http://archives.postgresql.org/pgsql-hackers/2002-03/msg00591.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
611
                  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01615.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
612
                  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
613
</p>
614
      </li><li>Allow function parameters to be passed by name,
Bruce Momjian's avatar
Fix:  
Bruce Momjian committed
615
                  get_employee_salary(12345 AS emp_id, 2001 AS tax_year)
Bruce Momjian's avatar
Bruce Momjian committed
616
      </li><li>Add Oracle-style packages  (Pavel)
Bruce Momjian's avatar
Bruce Momjian committed
617
<p>                  A package would be a schema with session-local variables,
Bruce Momjian's avatar
Bruce Momjian committed
618
                  public/private functions, and initialization functions.  It
Bruce Momjian's avatar
Bruce Momjian committed
619 620 621
                  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
622
                  <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
623
</p>
624 625 626 627 628 629 630 631 632 633
      </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
634 635 636 637
      </li><li>Add support for WITH HOLD and SCROLL cursors
<p>                  PL/pgSQL cursors should support the same syntax as
                  backend cursors.
</p>
638 639
      </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
640 641 642 643
</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
644
</p>
645 646 647 648 649 650 651 652 653
    </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
654 655
      </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
656
</p>
657
    </li></ul>
658 659
  </li></ul>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
660
<h1><a name="section_9">Clients</a></h1>
661 662

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
663
  <li>Have pg_ctl look at PGHOST in case it is a socket directory?
664 665 666 667 668 669
  </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.
670
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
671 672 673
  </li><li>Make consistent use of long/short command options --- pg_ctl needs
  long ones, pg_config doesn't have short ones, postgres doesn't have
  enough long ones, etc.
674 675 676 677 678 679 680 681
  </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
682
    </li><li>Fix psql's \d commands more consistent
Bruce Momjian's avatar
Bruce Momjian committed
683
<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
684
          <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
685
</p>
686 687 688
    </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
Add:  
Bruce Momjian committed
689 690 691
    </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
692 693 694 695 696 697 698 699
</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
700
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
701 702
    </li><li>Consider parsing the -c string into individual queries so each
          is run in its own transaction
703
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00291.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
704 705 706
</p>
    </li><li>Add \# to list command history like \s, but with line numbers
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php</a>
707
</p>
708
  </li></ul>
709 710
  </li><li>pg_dump
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
711
    <li>%Add dumping of comments on index columns and composite type columns
Bruce Momjian's avatar
Bruce Momjian committed
712
    </li><li>%Add full object name to the tag field.  eg. for operators we need
713
          '=(integer, integer)', instead of just '='.
Bruce Momjian's avatar
Bruce Momjian committed
714 715 716
    </li><li>Add pg_dumpall custom format dumps?
    </li><li>Remove unnecessary function pointer abstractions in pg_dump source
          code
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
717 718 719 720
    </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
721
    </li><li>Add options like pg_restore -l and -L to pg_dump
Bruce Momjian's avatar
Bruce Momjian committed
722
    </li><li>Stop dumping CASCADE on DROP TYPE commands in clean mode
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
723 724
    </li><li>Allow pg_dump --clean to drop roles that own objects or have
          privileges
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
725
    </li><li>-<em>Add -f to pg_dumpall</em>
726
  </li></ul>
727
  </li><li>ecpg
728 729 730 731 732
  <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
733
    </li><li>Solve cardinality &gt; 1 for input descriptors / variables?
734 735 736 737 738
    </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
739
    </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
740 741
    </li><li>Make SET CONNECTION thread-aware, non-standard?
    </li><li>Allow multidimensional arrays
Bruce Momjian's avatar
Bruce Momjian committed
742
    </li><li>Add internationalized message strings
Bruce Momjian's avatar
Bruce Momjian committed
743
    </li><li>Implement COPY FROM STDIN
744
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
745 746
  </li><li>libpq
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
747
    <li>Add PQescapeIdentifierConn()
Bruce Momjian's avatar
Bruce Momjian committed
748
    </li><li>Prevent PQfnumber() from lowercasing unquoted the column name
749 750 751
<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
752
    </li><li>Allow statement results to be automatically batched to the client
Bruce Momjian's avatar
Bruce Momjian committed
753
<p>          Currently, all statement results are transferred to the libpq
754 755
          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
756
          use of the first result rows while the rest are transferred, or
757
          held on the server waiting for them to be requested by libpq.
758
          One complexity is that a statement like SELECT 1/col could error
759
          out mid-way through the result set.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
760
    <li>Fix SSL retry to avoid useless repeated connection attempts and
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
761
          ensuing misleading error messages
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
762 763
    </li><li>Consider disallowing multiple queries in PQexec() as an
          additional barrier to SQL injection attacks
764 765
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00184.php</a>
</p>
Bruce Momjian's avatar
Bruce Momjian committed
766
  </li></ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
767
</p></ul>
Bruce Momjian's avatar
Bruce Momjian committed
768
<h1><a name="section_10">Triggers</a></h1>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
769

770
<ul>
Bruce Momjian's avatar
Bruce Momjian committed
771
  <li>Add deferred trigger queue file
772 773 774
<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
775
</p>
776 777 778 779
  </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
780
  TRIGGER requires a table lock so it is not ideal for this usage.
781 782 783 784 785 786
</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
787
  </li><li>Support triggers on columns
788
<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
789
</p>
790 791 792 793 794
  </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.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
795 796 797
</p>
  </li><li>Tighten trigger permission checks
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php</a>
798 799
</p>
</li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
800
<h1><a name="section_11">Dependency Checking</a></h1>
801 802

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
803 804 805
  <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
806 807 808
<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>
809
  </li><li>Track dependencies in function bodies and recompile/invalidate
Bruce Momjian's avatar
Bruce Momjian committed
810 811
<p>  This is particularly important for references to temporary tables
  in PL/PgSQL because PL/PgSQL caches query plans.  The only workaround
812 813 814
  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
815
</p>
816
</li></ul>
817
<h1><a name="section_12">Indexes</a></h1>
818

Bruce Momjian's avatar
Bruce Momjian committed
819
<ul>
820
  <li>Add UNIQUE capability to non-btree indexes
Bruce Momjian's avatar
Bruce Momjian committed
821 822 823 824 825 826 827 828 829
  </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
830 831 832
</p>
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php">http://archives.postgresql.org/pgsql-patches/2005-07/msg00512.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
833 834 835 836 837 838
</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
839
  </li><li>-<em>Allow the creation of indexes with mixed ascending/descending</em>
Bruce Momjian's avatar
Bruce Momjian committed
840
  specifiers
Bruce Momjian's avatar
Bruce Momjian committed
841
  </li><li>Consider compressing indexes by storing key values duplicated in
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
842
  several rows as a single index entry
Bruce Momjian's avatar
Bruce Momjian committed
843
<p>  This is difficult because it requires datatype-specific knowledge.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
844 845 846 847 848 849
</p>
  </li><li>Add REINDEX CONCURRENTLY, like CREATE INDEX CONCURRENTLY
<p>  This is difficult because you must upgrade to an exclusive table lock
  to replace the existing index file.  CREATE INDEX CONCURRENTLY does not
  have this complication.  This would allow index compaction without
  downtime.
Bruce Momjian's avatar
Bruce Momjian committed
850
</p>
851 852 853 854 855 856 857 858 859 860 861 862
  </li><li>Inheritance
  <ul>
    <li>Allow inherited tables to inherit indexes, UNIQUE constraints,
          and primary/foreign keys
    </li><li>Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
          on inherited table, e.g.  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 multiple tables.
</p>
    </li><li>Allow SELECT ... FOR UPDATE on inherited tables
  </li></ul>
863 864 865 866 867 868
  </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
869 870 871
  </li><li>Hash
  <ul>
    <li>Pack hash index buckets onto disk pages more efficiently
Bruce Momjian's avatar
Bruce Momjian committed
872
<p>          Currently only one hash bucket can be stored on a page. Ideally
Bruce Momjian's avatar
Bruce Momjian committed
873 874
          several hash buckets could be stored on a single page and greater
          granularity used for the hash algorithm.
875 876
</p>
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php">http://archives.postgresql.org/pgsql-hackers/2004-06/msg00168.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
877 878 879 880 881
</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
882 883
    </li><li>Add WAL logging for crash recovery
    </li><li>Allow multi-column hash indexes
Bruce Momjian's avatar
Bruce Momjian committed
884 885
  </li></ul>
</li></ul>
886
<h1><a name="section_13">Fsync</a></h1>
887 888 889 890

<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
891
<p>  Ideally this requires a separate test program that can be run
Bruce Momjian's avatar
Bruce Momjian committed
892 893
  at initdb time or optionally later.  Consider O_SYNC when
  O_DIRECT exists.
Bruce Momjian's avatar
Bruce Momjian committed
894
</p>
Bruce Momjian's avatar
Bruce Momjian committed
895
  </li><li>%Add an option to sync() before fsync()'ing checkpoint files
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
896
  </li><li>Add program to test if fsync has a delay compared to non-fsync
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
897 898
  </li><li>Reduce checkpoint performance degredation by forcing data to disk
  more evenly
Bruce Momjian's avatar
Bruce Momjian committed
899 900
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php">http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
901 902
  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php</a>
</p>
903
</li></ul>
904
<h1><a name="section_14">Cache Usage</a></h1>
Bruce Momjian's avatar
Bruce Momjian committed
905

906 907 908 909 910 911 912 913 914 915 916 917 918 919 920
<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.
921 922 923 924 925 926
</p>
  </li><li>Provide a way to calculate an "estimated COUNT(*)"
<p>  Perhaps by using the optimizer's cardinality estimates or random
  sampling.
</p>
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php">http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php</a>
927 928
</p>
  </li><li>Allow data to be pulled directly from indexes
Bruce Momjian's avatar
Bruce Momjian committed
929 930
<p>  Currently indexes do not have enough tuple visibility information 
  to allow data to be pulled from the index without also accessing 
931
  the heap.  One way to allow this is to set a bit on index tuples 
Bruce Momjian's avatar
Bruce Momjian committed
932 933
  to indicate if a tuple is currently visible to all transactions 
  when the first valid heap lookup happens.  This bit would have to 
934 935 936 937 938 939 940 941
  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.
942
</p>
943
  </li><li>Consider automatic caching of statements at various levels:
944 945 946 947 948 949
  <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
950
  sequential scans, also called "Synchronised Scanning"
951 952 953 954
<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
Bruce Momjian committed
955
</p>
Bruce Momjian's avatar
Bruce Momjian committed
956 957 958
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php">http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
959 960 961
</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>
962
</p>
963
</li></ul>
964
<h1><a name="section_15">Vacuum</a></h1>
965 966 967

<ul>
  <li>Improve speed with indexes
Bruce Momjian's avatar
Bruce Momjian committed
968
<p>  For large table adjustments during VACUUM FULL, it is faster to 
Bruce Momjian's avatar
Bruce Momjian committed
969 970
  reindex rather than update the index.  Also, index updates can
  bloat the index.
971
</p>
Bruce Momjian's avatar
Bruce Momjian committed
972 973
  </li><li>Reduce lock time during VACUUM FULL by moving tuples with read lock,
  then write lock and truncate table
974 975 976
<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
977
</p>
Bruce Momjian's avatar
Bruce Momjian committed
978 979
  </li><li>Auto-fill the free space map by scanning the buffer cache or by
  checking pages written by the background writer
980
<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
981
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php">http://archives.postgresql.org/pgsql-hackers/2006-03/msg00011.php</a>
982
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
983 984 985 986 987
  </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
988 989 990 991
  One complexity is that index entries still have to be vacuumed, and
  doing this without an index scan (by using the heap values to find the
  index entry) might be slow and unreliable, especially for user-defined
  index functions.
Bruce Momjian's avatar
Bruce Momjian committed
992 993 994
</p>
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php</a>
995
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
996 997
  </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
998 999
  </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
1000 1001
  </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>
1002
  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg01025.php</a>
1003
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1004 1005 1006 1007 1008 1009
  </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.
1010
  <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
1011
  <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
1012
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1013 1014
  </li><li>Reuse index tuples that point to heap tuples that are not visible to 
  anyone?
1015 1016
  </li><li>Auto-vacuum
  <ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1017
    <li>Use free-space map information to guide refilling
Bruce Momjian's avatar
Bruce Momjian committed
1018 1019
    </li><li>%Issue log message to suggest VACUUM FULL if a table is nearly
          empty?
Bruce Momjian's avatar
Bruce Momjian committed
1020
    </li><li>Consider logging activity either to the logs or a system view
1021
    </li><li>-<em>Turn on by default</em>
Bruce Momjian's avatar
Bruce Momjian committed
1022 1023 1024 1025 1026 1027 1028
    </li><li>Allow multiple vacuums so large tables do not starve small
          tables
<p>          <a href="http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php">http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php</a>
</p>
    </li><li>Improve control of auto-vacuum
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php</a>
</p>
1029 1030
  </li></ul>
</li></ul>
1031
<h1><a name="section_16">Locking</a></h1>
1032 1033

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
1034
  <li>Fix priority ordering of read and write light-weight locks (Neil)
1035 1036
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00893.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php">http://archives.postgresql.org/pgsql-hackers/2004-11/msg00905.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1037 1038 1039 1040 1041
</p>
  </li><li>Fix problem when multiple subtransactions of the same outer transaction
  hold different types of locks, and one subtransaction aborts
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php">http://archives.postgresql.org/pgsql-hackers/2006-11/msg01011.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00001.php</a>
1042
</p>
1043
</li></ul>
1044
<h1><a name="section_17">Startup Time Improvements</a></h1>
1045 1046

<ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1047
  <li>Experiment with multi-threaded backend for backend creation [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>]
1048 1049
<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
1050
  database startup overhead, but a few operating systems (Win32,
Bruce Momjian's avatar
Bruce Momjian committed
1051
  Solaris) might benefit from threading.  Also explore the idea of
1052
  a single session using multiple threads to execute a statement faster.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1053 1054 1055
</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
1056 1057 1058 1059
  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.
1060 1061 1062 1063 1064 1065 1066
</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>
1067
<h1><a name="section_18">Write-Ahead Log</a></h1>
1068 1069 1070

<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
1071
<p>  Currently, to protect against partial disk page writes, we write
1072 1073 1074 1075
  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
1076
  <ul>
Bruce Momjian's avatar
Bruce Momjian committed
1077
    <li>When off, write CRC to WAL and check file system blocks
Bruce Momjian's avatar
Bruce Momjian committed
1078
           on recovery
Bruce Momjian's avatar
Bruce Momjian committed
1079 1080 1081
<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
1082 1083 1084
    </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
1085 1086 1087
           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
1088 1089
</p>
  </li></ul>
Bruce Momjian's avatar
Bruce Momjian committed
1090
  </li><li>Allow WAL traffic to be streamed to another server for stand-by
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1091
  replication
1092
  </li><li>Reduce WAL traffic so only modified values are written rather than
Bruce Momjian's avatar
Bruce Momjian committed
1093
  entire rows?
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1094
  </li><li>-<em>Allow the pg_xlog directory location to be specified during initdb</em>
1095
  with a symlink back to the /data location
Bruce Momjian's avatar
Bruce Momjian committed
1096
  </li><li>Allow WAL information to recover corrupted pg_controldata
1097
<p>  <a href="http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php">http://archives.postgresql.org/pgsql-patches/2006-06/msg00025.php</a>
1098
</p>
1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111
  </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
1112
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1113 1114
  </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
1115
<p>  Allow tables to bypass WAL writes and just fsync() dirty pages on
Bruce Momjian's avatar
Bruce Momjian committed
1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128
  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.
1129 1130
</p>
</li></ul>
1131
<h1><a name="section_19">Optimizer / Executor</a></h1>
1132 1133

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
1134
  <li>Improve selectivity functions for geometric operators
Bruce Momjian's avatar
Bruce Momjian committed
1135
  </li><li>Allow ORDER BY ... LIMIT # to select high/low value without sort or
1136
  index using a sequential scan for highest/lowest values
Bruce Momjian's avatar
Bruce Momjian committed
1137
<p>  Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
1138 1139
  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
1140
  MIN/MAX already does this, but not for LIMIT &gt; 1.
1141
</p>
1142 1143 1144
  </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
Bruce Momjian's avatar
Bruce Momjian committed
1145 1146
  </li><li>Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and
  actual row counts differ by a specified percentage
1147
  </li><li>Consider using hash buckets to do DISTINCT, rather than sorting
Bruce Momjian's avatar
Bruce Momjian committed
1148 1149
<p>  This would be beneficial when there are few distinct values.  This is
  already used by GROUP BY.
1150
</p>
1151
  </li><li>Log statements where the optimizer row estimates were dramatically
Bruce Momjian's avatar
Bruce Momjian committed
1152
  different from the number of rows actually found?
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1153 1154
  </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>.
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1155 1156 1157 1158
</p>
  </li><li>Improve merge join performance by allowing mark/restore of 
  tuple sources
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php">http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1159
</p>
1160
</li></ul>
1161
<h1><a name="section_20">Miscellaneous Performance</a></h1>
1162 1163 1164 1165 1166

<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.
Bruce Momjian's avatar
Bruce Momjian committed
1167
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00820.php</a>
1168
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1169
  </li><li>Use mmap() rather than SYSV shared memory or to write WAL files?
1170 1171 1172 1173 1174 1175 1176 1177 1178
<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
1179
  way to <u>prevent</u> I/O to disk from the dirty shared buffers so changes
1180 1181 1182
  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
1183 1184 1185 1186 1187 1188 1189 1190
  </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
1191
  could only see rows from another completed transaction. However,
Bruce Momjian's avatar
Bruce Momjian committed
1192 1193 1194 1195 1196
  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
1197
  proper visibility of the row's cmin, for example, for cursors.
Bruce Momjian's avatar
Bruce Momjian committed
1198 1199
</p>
<p>  One possible solution is to create a phantom cid which represents a
Bruce Momjian's avatar
Bruce Momjian committed
1200 1201
  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
1202
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1203 1204
  </li><li>Consider ways of storing rows more compactly on disk
  <ul>
1205 1206 1207 1208 1209 1210 1211
    <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
1212
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1213 1214
    </li><li>Reduce the row header size?
  </li></ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1215
  </li><li>Consider increasing NUM_CLOG_BUFFERS
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1216 1217
  </li><li>Consider having the background writer update the transaction status
  hint bits before writing out the page
1218
</li></ul>
1219
<h1><a name="section_21">Source Code</a></h1>
1220 1221 1222 1223

<ul>
  <li>Add use of 'const' for variables in source tree
  </li><li>Move some things from /contrib into main tree
Bruce Momjian's avatar
Bruce Momjian committed
1224
  </li><li>%Remove warnings created by -Wcast-align
1225 1226 1227 1228
  </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
1229
  </li><li>%Remove memory/file descriptor freeing before ereport(ERROR)
1230
  </li><li>Acquire lock on a relation before building a relcache entry for it
Bruce Momjian's avatar
Bruce Momjian committed
1231
  </li><li>%Promote debug_query_string into a server-side function current_query()
1232
  </li><li>Allow cross-compiling by generating the zic database on the target system
Bruce Momjian's avatar
Done:  
Bruce Momjian committed
1233
  </li><li>Improve NLS maintenance of libpgport messages linked onto applications
1234 1235 1236 1237 1238 1239
  </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
Add:  
Bruce Momjian committed
1240
  </li><li>Fix sgmltools so PDFs can be generated with bookmarks
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1241 1242
  </li><li>Use UTF8 encoding for NLS messages so all server encodings can
  read them properly
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1243
  </li><li>Update Bonjour to work with newer cross-platform SDK
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1244 1245
  </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
1246
  </li><li>Consider detoasting keys before sorting
Bruce Momjian's avatar
Bruce Momjian committed
1247
  </li><li>Consider GnuTLS if OpenSSL license becomes a problem
1248
<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
Bruce Momjian committed
1249
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1250
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1251
  </li><li>Use strlcpy() rather than our StrNCpy() macro
Bruce Momjian's avatar
Bruce Momjian committed
1252
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php">http://archives.postgresql.org/pgsql-hackers/2006-09/msg02108.php</a>
1253
</p>
1254 1255
  </li><li>Consider changing documentation format from SGML to XML
<p>  <a href="http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php">http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
1256
</p>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1257 1258
  </li><li>Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h and
  consider making it more configurable in future releases
1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270
  </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
1271 1272 1273
    </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
1274 1275 1276
    </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
1277 1278 1279
          Win32 API, and we have to make sure MinGW handles it.  Another
          option is to wait for the MinGW project to fix it, or use the
          code from the LibGW32C project as a guide.
Bruce Momjian's avatar
Bruce Momjian committed
1280 1281
</p>
<p>          <a href="http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php">http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php</a>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1282
</p>
Bruce Momjian's avatar
Bruce Momjian committed
1283
    </li><li>Check WSACancelBlockingCall() for interrupts [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?win32intr">win32intr</a>]
1284 1285 1286 1287 1288 1289
  </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?
1290
    </li><li>Update clients to use data types, typmod, schema.table.column names
1291
          of result sets using new statement protocol
1292 1293
  </li></ul>
</li></ul>
1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318
<h1><a name="section_22">Exotic Features</a></h1>

<ul>
  <li>Add pre-parsing phase that converts non-ISO syntax to supported
  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
  </li><li>Allow statements across databases or servers with transaction
  semantics
<p>  This can be done using dblink and two-phase commit.
</p>
  </li><li>Add the features of packages
  <ul>
    <li>Make private objects accessible only to objects in the same schema
    </li><li>Allow current_schema.objname to access current schema objects
    </li><li>Add session variables
    </li><li>Allow nested schemas
  </li></ul>
  </li><li>Consider allowing control of upper/lower case folding of unquoted
  identifiers
<p>  <a href="http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php">http://archives.postgresql.org/pgsql-hackers/2004-04/msg00818.php</a>
1319
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg01527.php</a>
1320 1321
</p>
</li></ul>
1322
<h1><a name="section_23">Features We Do <u>Not</u> Want</a></h1>
1323 1324

<ul>
Bruce Momjian's avatar
Bruce Momjian committed
1325
  <li>All backends running as threads in a single process (not wanted)
1326 1327 1328 1329
<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
1330
  </li><li>Optimizer hints (not wanted)
1331 1332 1333
<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
1334 1335
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00517.php</a>
  <a href="http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php">http://archives.postgresql.org/pgsql-hackers/2006-10/msg00663.php</a>
Bruce Momjian's avatar
Bruce Momjian committed
1336 1337 1338 1339 1340
</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>
Bruce Momjian's avatar
Bruce Momjian committed
1341 1342
</p>
  </li><li>Embedded server (not wanted)
Bruce Momjian's avatar
Bruce Momjian committed
1343
<p>  While PostgreSQL clients runs fine in limited-resource environments, the
Bruce Momjian's avatar
Bruce Momjian committed
1344 1345 1346
  server requires multiple processes and a stable pool of resources to
  run reliabily and efficiently.  Stripping down the PostgreSQL server 
  to run in the same process address space as the client application 
1347
  would add too much complexity and failure cases.</p>
1348
</li></ul>
Bruce Momjian's avatar
Add:  
Bruce Momjian committed
1349
</li></ul></li></ul>
1350 1351
</body>
</html>