1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
2 "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
5 <title>PostgreSQL TODO List</title>
6 <meta name="generator" content="HTML::TextToHTML v2.25"/>
8 <body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
9 <h1><a name="section_1">PostgreSQL TODO List</a></h1>
10 <p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
11 Last updated: Tue Feb 28 14:47:56 EST 2006
13 <p>The most recent version of this document can be viewed at<br/>
14 <a href="http://www.postgresql.org/docs/faqs.TODO.html">http://www.postgresql.org/docs/faqs.TODO.html</a>.
16 <p><strong>A hyphen, "-", marks changes that will appear in the upcoming 8.2 release.</strong><br/>
17 <strong>A percent sign, "%", marks items that are easier to implement.</strong>
19 <p>Bracketed items, "[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]", have more detail.
21 <p>This list contains all known PostgreSQL bugs and feature requests. If<br/>
22 you would like to work on an item, please read the Developer's FAQ<br/>
25 <h1><a name="section_2">Administration</a></h1>
28 <li>%Remove behavior of postmaster -o
29 </li><li>-*%Allow pooled connections to list all prepared statements*
30 <p> This would allow an application inheriting a pooled connection to know
31 the statements prepared in the current session.
33 </li><li>Allow major upgrades without dump/reload, perhaps using pg_upgrade
34 [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pg_upgrade">pg_upgrade</a>]
35 </li><li>Check for unreferenced table files created by transactions that were
36 in-progress when the server terminated abruptly
37 </li><li>Allow administrators to safely terminate individual sessions either
38 via an SQL function or SIGTERM
39 <p> Lock table corruption following SIGTERM of an individual backend
40 has been reported in 8.0. A possible cause was fixed in 8.1, but
41 it is unknown whether other problems exist. This item mostly
42 requires additional testing rather than of writing any new code.
44 </li><li>%Set proper permissions on non-system schemas during db creation
45 <p> Currently all schemas are owned by the super-user because they are
46 copied from the template1 database.
48 </li><li>Support table partitioning that allows a single table to be stored
49 in subtables that are partitioned based on the primary key or a WHERE
51 </li><li>Add function to report the time of the most recent server reload
52 </li><li>Allow statistics collector information to be pulled from the collector
53 process directly, rather than requiring the collector to write a
54 filesystem file twice a second?
55 </li><li>Improve replication solutions
58 <p> You can use any of the master/slave replication servers to use a
59 standby server for data warehousing. To allow read/write queries to
60 multiple servers, you need multi-master replication like pgcluster.
62 </li><li>Allow replication over unreliable or non-persistent links
64 </li><li>Configuration files
66 <li>%Add "include file" functionality in postgresql.conf
67 </li><li>%Allow commenting of variables in postgresql.conf to restore them
69 <p> Currently, if a variable is commented out, it keeps the
70 previous uncommented value until a server restarted.
72 </li><li>%Allow pg_hba.conf settings to be controlled via SQL
73 <p> This would add a function to load the SQL table from
74 pg_hba.conf, and one to writes its contents to the flat file.
75 The table should have a line number that is a float so rows
76 can be inserted between existing rows, e.g. row 2.5 goes
77 between row 2 and row 3.
79 </li><li>Allow pg_hba.conf to specify host names along with IP addresses
80 <p> Host name lookup could occur when the postmaster reads the
81 pg_hba.conf file, or when the backend starts. Another
82 solution would be to reverse lookup the connection IP and
83 check that hostname against the host names in pg_hba.conf.
84 We could also then check that the host name maps to the IP
87 </li><li>%Allow postgresql.conf file values to be changed via an SQL
88 API, perhaps using SET GLOBAL
89 </li><li>Allow the server to be stopped/restarted via an SQL API
90 </li><li>-<em>Issue a warning if a change-on-restart-only postgresql.conf value</em>
91 is modified and the server config files are reloaded
92 </li><li>Mark change-on-restart-only values in postgresql.conf
96 <li>Allow a database in tablespace t1 with tables created in
97 tablespace t2 to be used as a template for a new database created
98 with default tablespace t2
99 <p> All objects in the default database tablespace must have default
100 tablespace specifications. This is because new databases are
101 created by copying directories. If you mix default tablespace
102 tables and tablespace-specified tables in the same directory,
103 creating a new database from such a mixed directory would create a
104 new database with tables that had incorrect explicit tablespaces.
105 To fix this would require modifying pg_class in the newly copied
106 database, which we don't currently do.
108 </li><li>Allow reporting of which objects are in which tablespaces
109 <p> This item is difficult because a tablespace can contain objects
110 from multiple databases. There is a server-side function that
111 returns the databases which use a specific tablespace, so this
112 requires a tool that will call that function and connect to each
113 database to find the objects in each database for that tablespace.
116 <li>%Add a GUC variable to control the tablespace for temporary objects
118 <p> It could start with a random tablespace from a supplied list and
119 cycle through the list.
121 </li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
122 structure on the recovery computer is different from the original
123 </li><li>Allow per-tablespace quotas
126 </li><li>Point-In-Time Recovery (PITR)
128 <li>Allow point-in-time recovery to archive partially filled
129 write-ahead logs [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
130 <p> Currently only full WAL files are archived. This means that the
131 most recent transactions aren't available for recovery in case
132 of a disk failure. This could be triggered by a user command or
135 </li><li>Automatically force archiving of partially-filled WAL files when
136 pg_stop_backup() is called or the server is stopped
137 <p> Doing this will allow administrators to know more easily when
138 the archive contains all the files needed for point-in-time
141 </li><li>%Create dump tool for write-ahead logs for use in determining
142 transaction id for point-in-time recovery
143 </li><li>Allow a warm standby system to also allow read-only statements
144 [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
145 <p> This is useful for checking PITR recovery.
147 </li><li>Allow the PITR process to be debugged and data examined
150 <h1><a name="section_3">Monitoring</a></h1>
153 <li>Allow server log information to be output as INSERT statements
154 <p> This would allow server log information to be easily loaded into
155 a database for analysis.
157 </li><li>%Add ability to monitor the use of temporary sort files
158 </li><li>Allow server logs to be remotely read and removed using SQL commands
159 </li><li>Allow protocol-level BIND parameter values to be logged
161 <h1><a name="section_4">Data Types</a></h1>
164 <li>Improve the MONEY data type
165 <p> Change the MONEY data type to use DECIMAL internally, with special
166 locale-aware output formatting.
168 </li><li>Change NUMERIC to enforce the maximum precision
169 </li><li>Add NUMERIC division operator that doesn't round?
170 <p> Currently NUMERIC _rounds_ the result to the specified precision.
171 This means division can return a result that multiplied by the
172 divisor is greater than the dividend, e.g. this returns a value > 10:
175 <p> SELECT (10::numeric(2,0) / 6::numeric(2,0))::numeric(2,0) * 6;
177 <p> The positive modulus result returned by NUMERICs might be considered<br/>
178 inaccurate, in one sense.
181 <li>%Disallow changing default expression of a SERIAL column
182 </li><li>Fix data types where equality comparison isn't intuitive, e.g. box
183 </li><li>-<em>Zero umasked bits in conversion from INET cast to CIDR</em>
184 </li><li>-<em>Prevent INET cast to CIDR from dropping netmask, SELECT '<a href="telnet://1.1.1.1">1.1.1.1</a>'::inet::cidr</em>
185 </li><li>-<em>Allow INET + INT8 to increment the host part of the address or</em>
186 throw an error on overflow
187 </li><li>-<em>Add 'tid != tid ' operator for use in corruption recovery</em>
188 </li><li>Allow user-defined types to specify a type modifier at table creation
190 </li><li>Dates and Times
192 <li>Allow infinite dates and intervals just like infinite timestamps
193 </li><li>Merge hardwired timezone names with the TZ database; allow either
194 kind everywhere a TZ name is currently taken
195 </li><li>Allow customization of the known set of TZ names (generalize the
196 present australian_timezones hack)
197 </li><li>Allow TIMESTAMP WITH TIME ZONE to store the original timezone
198 information, either zone name or offset from UTC [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?timezone">timezone</a>]
199 <p> If the TIMESTAMP value is stored with a time zone name, interval
200 computations should adjust based on the time zone rules.
202 </li><li>Fix SELECT '0.01 years'::interval, '0.01 months'::interval
203 </li><li>Fix SELECT INTERVAL '1' MONTH
204 </li><li>Add a GUC variable to allow output of interval values in ISO8601
206 </li><li>Improve timestamptz subtraction to be DST-aware
207 <p> Currently, subtracting one date from another that crosses a
208 daylight savings time adjustment can return '1 day 1 hour', but
209 adding that back to the first date returns a time one hour in
210 the future. This is caused by the adjustment of '25 hours' to
211 '1 day 1 hour', and '1 day' is the same time the next day, even
212 if daylight savings adjustments are involved.
214 </li><li>Fix interval display to support values exceeding 2^31 hours
215 </li><li>Add overflow checking to timestamp and interval arithmetic
216 </li><li>Add ISO INTERVAL handling
218 <li>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO
220 </li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
221 </li><li>For syntax that isn't uniquely ISO or PG syntax, like '1:30' or
222 '1', treat as ISO if there is a range specification clause,
223 and as PG if there no clause is present, e.g. interpret
224 <p> '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and
225 interpret '1:30' as '1 hour, 30 minutes'
226 <li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
227 INTERVAL MONTH), and this should return '12 months'
228 </li><li>Round or truncate values to the requested precision, e.g.
229 INTERVAL '11 months' AS YEAR should return one or zero
230 </li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
235 <li>-<em>Allow NULLs in arrays</em>
236 </li><li>Delay resolution of array expression's data type so assignment
237 coercion can be performed on empty array expressions
241 <li>Improve vacuum of large objects, like /contrib/vacuumlo?
242 </li><li>Add security checking for large objects
243 </li><li>Auto-delete large objects when referencing row is deleted
244 <p> /contrib/lo offers this functionality.
246 </li><li>Allow read/write into TOAST values like large objects
247 <p> This requires the TOAST column to be stored EXTERNAL.
251 <h1><a name="section_5">Functions</a></h1>
254 <li>Allow INET subnet tests using non-constants to be indexed
255 </li><li>Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
257 <p> Current CURRENT_TIMESTAMP returns the start time of the current
258 transaction, and gettimeofday() returns the wallclock time. This will
259 make time reporting more consistent and will allow reporting of
260 the statement start time.
262 </li><li>%Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
263 pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
264 </li><li>-<em>Allow to_char() to print localized month names</em>
265 </li><li>Allow functions to have a schema search path specified at creation time
266 </li><li>Allow substring/replace() to get/set bit values
267 </li><li>Allow to_char() on interval values to accumulate the highest unit
269 <p> Some special format flag would be required to request such
270 accumulation. Such functionality could also be added to EXTRACT.
271 Prevent accumulation that crosses the month/day boundary because of
272 the uneven number of days in a month.
275 <li>to_char(INTERVAL '1 hour 5 minutes', 'MI') => 65
276 </li><li>to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600
277 </li><li>to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
278 </li><li>to_char(INTERVAL '3 years 5 months','MM') => 41
280 </li><li>-<em>Add sleep() function, remove from regress.c</em>
281 </li><li>Allow user-defined functions retuning a domain value to enforce domain
283 </li><li>Add SPI_gettypmod() to return the typemod for a TupleDesc
285 <h1><a name="section_6">Multi-Language Support</a></h1>
288 <li>Add NCHAR (as distinguished from ordinary varchar),
289 </li><li>Allow locale to be set at database creation
290 <p> Currently locale can only be set during initdb. No global tables have
291 locale-aware columns. However, the database template used during
292 database creation might have locale-aware indexes. The indexes would
293 need to be reindexed to match the new locale.
295 </li><li>Allow encoding on a per-column basis
296 <p> Right now only one encoding is allowed per database.
298 </li><li>Support multiple simultaneous character sets, per SQL92
299 </li><li>Improve UTF8 combined character handling?
300 </li><li>Add octet_length_server() and octet_length_client()
301 </li><li>Make octet_length_client() the same as octet_length()?
302 </li><li>Fix problems with wrong runtime encoding conversion for NLS message files
304 <h1><a name="section_7">Views / Rules</a></h1>
307 <li>Automatically create rules on views so they are updateable, per SQL99
308 <p> We can only auto-create rules for simple views. For more complex
309 cases users will still have to write rules manually.
311 </li><li>Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
312 </li><li>Allow NOTIFY in rules involving conditionals
313 </li><li>Allow VIEW/RULE recompilation when the underlying tables change
314 <p> Another issue is whether underlying table changes should be reflected
315 in the view, e.g. should SELECT * show additional columns if they
316 are added after the view is created.
319 <h1><a name="section_8">SQL Commands</a></h1>
322 <li>Change LIMIT/OFFSET and FETCH/MOVE to use int8
323 </li><li>Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
324 </li><li>Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
325 </li><li>%Allow SET CONSTRAINTS to be qualified by schema/table name
326 </li><li>%Allow TRUNCATE ... CASCADE/RESTRICT
327 <p> This is like DELETE CASCADE, but truncates.
329 </li><li>%Add a separate TRUNCATE permission
330 <p> Currently only the owner can TRUNCATE a table because triggers are not
331 called, and the table is locked in exclusive mode.
333 </li><li>Allow PREPARE of cursors
334 </li><li>-<em>Allow PREPARE to automatically determine parameter types based on the SQL</em>
336 </li><li>Allow finer control over the caching of prepared query plans
337 <p> Currently, queries prepared via the libpq API are planned on first
338 execute using the supplied parameters --- allow SQL PREPARE to do the
339 same. Also, allow control over replanning prepared queries either
340 manually or automatically when statistics for execute parameters
341 differ dramatically from those used during planning.
343 </li><li>Allow LISTEN/NOTIFY to store info in memory rather than tables?
344 <p> Currently LISTEN/NOTIFY information is stored in pg_listener. Storing
345 such information in memory would improve performance.
347 </li><li>Add optional textual message to NOTIFY
348 <p> This would allow an informational message to be added to the notify
349 message, perhaps indicating the row modified or other custom
352 </li><li>Add a GUC variable to warn about non-standard SQL usage in queries
353 </li><li>Add SQL-standard MERGE command, typically used to merge two tables
354 [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
355 <p> This is similar to UPDATE, then for unmatched rows, INSERT.
356 Whether concurrent access allows modifications which could cause
357 row loss is implementation independent.
359 </li><li>Add REPLACE or UPSERT command that does UPDATE, or on failure, INSERT
360 [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?merge">merge</a>]
361 <p> To implement this cleanly requires that the table have a unique index
362 so duplicate checking can be easily performed. It is possible to
363 do it without a unique index if we require the user to LOCK the table
366 </li><li>Add NOVICE output level for helpful messages like automatic sequence/index
368 </li><li>-<em>Add COMMENT ON for all cluster global objects (roles, databases</em>
370 </li><li>-<em>Make row-wise comparisons work per SQL spec</em>
371 <p> Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but
372 the SQL standard requires it to be processed as a column-by-column
373 comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.
375 </li><li>Add RESET CONNECTION command to reset all session state
376 <p> This would include resetting of all variables (RESET ALL), dropping of
377 temporary tables, removing any NOTIFYs, cursors, open transactions,
378 prepared queries, currval()s, etc. This could be used for connection
379 pooling. We could also change RESET ALL to have this functionality.
380 The difficult of this features is allowing RESET ALL to not affect
381 changes made by the interface driver for its internal use. One idea
382 is for this to be a protocol-only feature. Another approach is to
383 notify the protocol when a RESET CONNECTION command is used.
385 </li><li>Add GUC to issue notice about statements that use unjoined tables
386 </li><li>Allow EXPLAIN to identify tables that were skipped because of
388 </li><li>Allow EXPLAIN output to be more easily processed by scripts
389 </li><li>Eventually enable escape_string<u>warning and standard</u>conforming_strings
390 </li><li>Simplify dropping roles that have objects in several databases
391 </li><li>Allow COMMENT ON to accept an expression rather than just a string
392 </li><li>Allow the count returned by SELECT, etc to be to represent as an int64
393 to allow a higher range of values
394 </li><li>Make CLUSTER preserve recently-dead tuples per MVCC requirements
395 </li><li>Add SQL99 WITH clause to SELECT
396 </li><li>Add SQL99 WITH RECURSIVE to SELECT
399 <li>Allow CREATE TABLE AS to determine column lengths for complex
400 expressions like SELECT col1 || col2
401 </li><li>Use more reliable method for CREATE DATABASE to get a consistent
403 </li><li>-<em>Add ON COMMIT capability to CREATE TABLE AS ... SELECT</em>
407 <li>Allow UPDATE to handle complex aggregates [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?update">update</a>]?
408 </li><li>-<em>Allow an alias to be provided for the target table in</em>
410 </li><li>Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple
415 <li>%Have ALTER TABLE RENAME rename SERIAL sequence names
416 </li><li>Add ALTER DOMAIN to modify the underlying data type
417 </li><li>%Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
418 </li><li>%Allow ALTER TABLE to change constraint deferrability and actions
419 </li><li>Add missing object types for ALTER ... SET SCHEMA
420 </li><li>Allow ALTER TABLESPACE to move to different directories
421 </li><li>Allow databases to be moved to different tablespaces
422 </li><li>Allow moving system tables to other tablespaces, where possible
423 <p> Currently non-global system tables must be in the default database
424 tablespace. Global system tables can never be moved.
426 </li><li>%Prevent child tables from altering or dropping constraints
427 like CHECK that were inherited from the parent table
428 </li><li>Have ALTER INDEX update the name of a constraint using that index
429 </li><li>Add ALTER TABLE RENAME CONSTRAINT, update index name also
433 <li>Automatically maintain clustering on a table
434 <p> This might require some background daemon to maintain clustering
435 during periods of low usage. It might also require tables to be only
436 partially filled for easier reorganization. Another idea would
437 be to create a merged heap/index data file so an index lookup would
438 automatically access the heap data too. A third idea would be to
439 store heap rows in hashed groups, perhaps using a user-supplied
442 </li><li>%Add default clustering to system tables
443 <p> To do this, determine the ideal cluster index for each system
444 table and set the cluster setting during initdb.
449 <li>Allow COPY to report error lines and continue
450 <p> This requires the use of a savepoint before each COPY line is
451 processed, with ROLLBACK on COPY failure.
453 </li><li>%Have COPY return the number of rows loaded/unloaded?
454 </li><li>Allow COPY on a newly-created table to skip WAL logging
455 <p> On crash recovery, the table involved in the COPY would
456 be removed or have its heap and index files truncated. One
457 issue is that no other backend should be able to add to
458 the table at the same time, which is something that is
461 </li><li>Allow COPY to output from views
462 <p> Another idea would be to allow actual SELECT statements in a COPY.
465 </li><li>GRANT/REVOKE
467 <li>Allow column-level privileges
468 </li><li>%Allow GRANT/REVOKE permissions to be applied to all schema objects
470 <p> The proposed syntax is:
471 </p><p> GRANT SELECT ON ALL TABLES IN public TO phpuser;
472 GRANT SELECT ON NEW TABLES IN public TO phpuser;
475 <li>Allow GRANT/REVOKE permissions to be inherited by objects based on
477 </li><li>Allow SERIAL sequences to inherit permissions from the base table?
482 <li>Allow UPDATE/DELETE WHERE CURRENT OF cursor
483 <p> This requires using the row ctid to map cursor rows back to the
484 original heap row. This become more complicated if WITH HOLD cursors
485 are to be supported because WITH HOLD cursors have a copy of the row
486 and no FOR UPDATE lock.
488 </li><li>Prevent DROP TABLE from dropping a row referenced by its own open
490 </li><li>-<em>Allow pooled connections to list all open WITH HOLD cursors</em>
491 <p> Because WITH HOLD cursors exist outside transactions, this allows
492 them to be listed so they can be closed.
497 <li>Allow INSERT/UPDATE of the system-generated oid value for a row
498 </li><li>Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
499 </li><li>Allow INSERT/UPDATE ... RETURNING new.col or old.col
500 <p> This is useful for returning the auto-generated key for an INSERT.
501 One complication is how to handle rules that run as part of
507 <li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
509 </li><li>Add SET PATH for schemas?
510 <p> This is basically the same as SET search_path.
513 </li><li>Server-Side Languages
515 <li>Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
516 </li><li>Allow function parameters to be passed by name,
517 get_employee_salary(emp_id => 12345, tax_year => 2001)
518 </li><li>Add Oracle-style packages
519 </li><li>Add table function support to pltcl, plpython
520 </li><li>Add capability to create and call PROCEDURES
521 </li><li>Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]
522 </li><li>Allow function argument names to be statements from PL/PgSQL
523 </li><li>Add MOVE to PL/pgSQL
524 </li><li>Add support for polymorphic arguments and return types to
525 languages other than PL/PgSQL
526 </li><li>Add support for OUT and INOUT parameters to languages other
528 </li><li>Add single-step debugging of PL/PgSQL functions
529 </li><li>Allow PL/PgSQL to support WITH HOLD cursors
532 <h1><a name="section_9">Clients</a></h1>
535 <li>-<em>Have initdb set the input DateStyle (MDY or DMY) based on locale</em>
536 </li><li>Have pg_ctl look at PGHOST in case it is a socket directory?
537 </li><li>Allow pg_ctl to work properly with configuration files located outside
539 <p> pg_ctl can not read the pid file because it isn't located in the
540 config directory but in the PGDATA directory. The solution is to
541 allow pg_ctl to read and understand postgresql.conf to find the
542 data_directory value.
546 <li>Have psql show current values for a sequence
547 </li><li>Move psql backslash database information into the backend, use
548 mnemonic commands? [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?psql">psql</a>]
549 <p> This would allow non-psql clients to pull the same information out
550 of the database as psql.
552 </li><li>Fix psql's display of schema information (Neil)
553 </li><li>Allow psql \pset boolean variables to set to fixed values, rather
555 </li><li>Consistently display privilege information for all objects in psql
556 </li><li>-<em>Improve psql's handling of multi-line statements</em>
557 <p> Currently, while \e saves a single statement as one entry, interactive
558 statements are saved one line at a time. Ideally all statements
559 would be saved like \e does.
561 </li><li>-<em>Allow multi-line column values to align in the proper columns</em>
562 <p> If the second output column value is 'a\nb', the 'b' should appear
563 in the second display column, rather than the first column as it
566 </li><li>Display IN, INOUT, and OUT parameters in \df+
567 <p> It probably requires psql to output newlines in the proper
568 column, which is already on the TODO list.
570 </li><li>Add auto-expanded mode so expanded output is used if the row
571 length is wider than the screen width.
572 <p> Consider using auto-expanded mode for backslash commands like \df+.
574 </li><li>Prevent tab completion of SET TRANSACTION from querying the
575 database and therefore preventing the transaction isolation
576 level from being set.
577 <p> Currently, SET <tab> causes a database lookup to check all
578 supported session variables. This query causes problems
579 because setting the transaction isolation level must be the
580 first statement of a transaction.
585 <li>%Have pg_dump use multi-statement transactions for INSERT dumps
586 </li><li>%Allow pg_dump to use multiple -t and -n switches [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pg_dump">pg_dump</a>]
587 </li><li>%Add dumping of comments on index columns and composite type columns
588 </li><li>%Add full object name to the tag field. eg. for operators we need
589 '=(integer, integer)', instead of just '='.
590 </li><li>Add pg_dumpall custom format dumps?
591 </li><li>%Add CSV output format
592 </li><li>Update pg_dump and psql to use the new COPY libpq API (Christopher)
593 </li><li>Remove unnecessary function pointer abstractions in pg_dump source
595 </li><li>Allow selection of individual object(s) of all types, not just
597 </li><li>In a selective dump, allow dumping of an object and all its
599 </li><li>Add options like pg_restore -l and -L to pg_dump
600 </li><li>Stop dumping CASCADE on DROP TYPE commands in clean mode
601 </li><li>Allow pg_dump --clean to drop roles that own objects or have
603 </li><li>Add -f to pg_dumpall
608 <p> Document differences between ecpg and the SQL standard and
609 information about the Informix-compatibility module.
611 </li><li>Solve cardinality > 1 for input descriptors / variables?
612 </li><li>Add a semantic check level, e.g. check if a table really exists
613 </li><li>fix handling of DB attributes that are arrays
614 </li><li>Use backend PREPARE/EXECUTE facility for ecpg where possible
615 </li><li>Implement SQLDA
616 </li><li>Fix nested C comments
617 </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
618 </li><li>Make SET CONNECTION thread-aware, non-standard?
619 </li><li>Allow multidimensional arrays
620 </li><li>Add internationalized message strings
626 <li>Add a function to support Parse/DescribeStatement capability
627 </li><li>Add PQescapeIdentifier()
628 </li><li>Prevent PQfnumber() from lowercasing unquoted the column name
629 <p> PQfnumber() should never have been doing lowercasing, but
630 historically it has so we need a way to prevent it
632 </li><li>Allow statement results to be automatically batched to the client
633 <p> Currently, all statement results are transferred to the libpq
634 client before libpq makes the results available to the
635 application. This feature would allow the application to make
636 use of the first result rows while the rest are transferred, or
637 held on the server waiting for them to be requested by libpq.
638 One complexity is that a statement like SELECT 1/col could error
639 out mid-way through the result set.
642 <h1><a name="section_10">Referential Integrity</a></h1>
645 <li>Add MATCH PARTIAL referential integrity
646 </li><li>Add deferred trigger queue file
647 <p> Right now all deferred trigger information is stored in backend
648 memory. This could exhaust memory for very large trigger queues.
649 This item involves dumping large queues into files.
651 </li><li>Change foreign key constraint for array -> element to mean element
653 </li><li>Allow DEFERRABLE UNIQUE constraints?
654 </li><li>Allow triggers to be disabled in only the current session.
655 <p> This is currently possible by starting a multi-statement transaction,
656 modifying the system tables, performing the desired SQL, restoring the
657 system tables, and committing the transaction. ALTER TABLE ...
658 TRIGGER requires a table lock so it is not ideal for this usage.
660 </li><li>With disabled triggers, allow pg_dump to use ALTER TABLE ADD FOREIGN KEY
661 <p> If the dump is known to be valid, allow foreign keys to be added
662 without revalidating the data.
664 </li><li>Allow statement-level triggers to access modified rows
665 </li><li>Support triggers on columns (Greg Sabino Mullane)
666 </li><li>Enforce referential integrity for system tables
667 </li><li>Allow AFTER triggers on system tables
668 <p> System tables are modified in many places in the backend without going
669 through the executor and therefore not causing triggers to fire. To
670 complete this item, the functions that modify system tables will have
674 <h1><a name="section_11">Dependency Checking</a></h1>
677 <li>Flush cached query plans when the dependent objects change,
678 when the cardinality of parameters changes dramatically, or
679 when new ANALYZE statistics are available
680 <p> A more complex solution would be to save multiple plans for different
681 cardinality and use the appropriate plan based on the EXECUTE values.
683 </li><li>Track dependencies in function bodies and recompile/invalidate
684 <p> This is particularly important for references to temporary tables
685 in PL/PgSQL because PL/PgSQL caches query plans. The only workaround
686 in PL/PgSQL is to use EXECUTE. One complexity is that a function
687 might itself drop and recreate dependent tables, causing it to
688 invalidate its own query plan.
691 <h1><a name="section_12">Exotic Features</a></h1>
694 <li>Add pre-parsing phase that converts non-ISO syntax to supported
696 <p> This could allow SQL written for other databases to run without
699 </li><li>Allow plug-in modules to emulate features from other databases
700 </li><li>SQL*Net listener that makes PostgreSQL appear as an Oracle database
702 </li><li>Allow statements across databases or servers with transaction
704 <p> This can be done using dblink and two-phase commit.
706 </li><li>Add the features of packages
708 <li>Make private objects accessible only to objects in the same schema
709 </li><li>Allow current_schema.objname to access current schema objects
710 </li><li>Add session variables
711 </li><li>Allow nested schemas
714 <h1><a name="section_13">Indexes</a></h1>
717 <li>Allow inherited tables to inherit index, UNIQUE constraint, and primary
719 </li><li>UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
720 inherited table: INSERT INTO inherit_table (unique_index_col) VALUES
722 <p> The main difficulty with this item is the problem of creating an index
723 that can span more than one table.
725 </li><li>Allow SELECT ... FOR UPDATE on inherited tables
726 </li><li>Add UNIQUE capability to non-btree indexes
727 </li><li>Prevent index uniqueness checks when UPDATE does not modify the column
728 <p> Uniqueness (index) checks are done when updating a column even if the
729 column is not modified by the UPDATE.
731 </li><li>Allow the creation of on-disk bitmap indexes which can be quickly
732 combined with other bitmap indexes
733 <p> Such indexes could be more compact if there are only a few distinct values.
734 Such indexes can also be compressed. Keeping such indexes updated can be
737 </li><li>Allow use of indexes to search for NULLs
738 <p> One solution is to create a partial index on an IS NULL expression.
740 </li><li>Allow accurate statistics to be collected on indexes with more than
741 one column or expression indexes, perhaps using per-index statistics
742 </li><li>Add fillfactor to control reserved free space during index creation
743 </li><li>Allow the creation of indexes with mixed ascending/descending specifiers
744 </li><li>Allow constraint_exclusion to work for UNIONs like it does for
745 inheritance, allow it to work for UPDATE and DELETE statements, and allow
746 it to be used for all statements with little performance impact
747 </li><li>Allow CREATE INDEX to take an additional parameter for use with
749 </li><li>Consider compressing indexes by storing key values duplicated in
750 several rows as a single index entry
751 <p> This is difficult because it requires datatype-specific knowledge.
755 <li>Add more GIST index support for geometric data types
756 </li><li>Allow GIST indexes to create certain complex index types, like
757 digital trees (see Aoki)
761 <li>Pack hash index buckets onto disk pages more efficiently
762 <p> Currently only one hash bucket can be stored on a page. Ideally
763 several hash buckets could be stored on a single page and greater
764 granularity used for the hash algorithm.
766 </li><li>Consider sorting hash buckets so entries can be found using a
767 binary search, rather than a linear scan
768 </li><li>In hash indexes, consider storing the hash value with or instead
770 </li><li>Add WAL logging for crash recovery
771 </li><li>Allow multi-column hash indexes
774 <h1><a name="section_14">Fsync</a></h1>
777 <li>Improve commit_delay handling to reduce fsync()
778 </li><li>Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
779 <p> Ideally this requires a separate test program that can be run
780 at initdb time or optionally later. Consider O_SYNC when
783 </li><li>%Add an option to sync() before fsync()'ing checkpoint files
784 </li><li>Add program to test if fsync has a delay compared to non-fsync
786 <h1><a name="section_15">Cache Usage</a></h1>
789 <li>Allow free-behind capability for large sequential scans, perhaps using
791 <p> Posix_fadvise() can control both sequential/random file caching and
792 free-behind behavior, but it is unclear how the setting affects other
793 backends that also have the file open, and the feature is not supported
794 on all operating systems.
796 </li><li>Speed up COUNT(*)
797 <p> We could use a fixed row count and a +/- count to follow MVCC
798 visibility rules, or a single cached value could be used and
799 invalidated if anyone modifies the table. Another idea is to
800 get a count directly from a unique index, but for this to be
801 faster than a sequential scan it must avoid access to the heap
802 to obtain tuple visibility information.
804 </li><li>Add estimated_count(*) to return an estimate of COUNT(*)
805 <p> This would use the planner ANALYZE statistics to return an estimated
808 </li><li>Allow data to be pulled directly from indexes
809 <p> Currently indexes do not have enough tuple visibility information
810 to allow data to be pulled from the index without also accessing
811 the heap. One way to allow this is to set a bit on index tuples
812 to indicate if a tuple is currently visible to all transactions
813 when the first valid heap lookup happens. This bit would have to
814 be cleared when a heap tuple is expired.
816 <p> Another idea is to maintain a bitmap of heap pages where all rows
817 are visible to all backends, and allow index lookups to reference
818 that bitmap to avoid heap lookups, perhaps the same bitmap we might
819 add someday to determine which heap pages need vacuuming. Frequently
820 accessed bitmaps would have to be stored in shared memory. One 8k
821 page of bitmaps could track 512MB of heap pages.
823 </li><li>Consider automatic caching of statements at various levels:
825 <li>Parsed query tree
826 </li><li>Query execute plan
827 </li><li>Query results
829 </li><li>Allow sequential scans to take advantage of other concurrent
830 sequential scans, also called "Synchronised Scanning"
831 <p> One possible implementation is to start sequential scans from the lowest
832 numbered buffer in the shared cache, and when reaching the end wrap
833 around to the beginning, rather than always starting sequential scans
834 at the start of the table.
837 <h1><a name="section_16">Vacuum</a></h1>
840 <li>Improve speed with indexes
841 <p> For large table adjustments during VACUUM FULL, it is faster to
842 reindex rather than update the index.
844 </li><li>Reduce lock time during VACUUM FULL by moving tuples with read lock,
845 then write lock and truncate table
846 <p> Moved tuples are invisible to other backends so they don't require a
847 write lock. However, the read lock promotion to write lock could lead
848 to deadlock situations.
850 </li><li>Auto-fill the free space map by scanning the buffer cache or by
851 checking pages written by the background writer
852 </li><li>Create a bitmap of pages that need vacuuming
853 <p> Instead of sequentially scanning the entire table, have the background
854 writer or some other process record pages that have expired rows, then
855 VACUUM can look at just those pages rather than the entire table. In
856 the event of a system crash, the bitmap would probably be invalidated.
857 One complexity is that index entries still have to be vacuumed, and
858 doing this without an index scan (by using the heap values to find the
859 index entry) might be slow and unreliable, especially for user-defined
862 </li><li>-<em>Add system view to show free space map contents</em>
865 <li>Use free-space map information to guide refilling
866 </li><li>%Issue log message to suggest VACUUM FULL if a table is nearly
868 </li><li>Improve xid wraparound detection by recording per-table rather
870 </li><li>Consider logging activity either to the logs or a system view
873 <h1><a name="section_17">Locking</a></h1>
876 <li>Fix priority ordering of read and write light-weight locks (Neil)
878 <h1><a name="section_18">Startup Time Improvements</a></h1>
881 <li>Experiment with multi-threaded backend [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>]
882 <p> This would prevent the overhead associated with process creation. Most
883 operating systems have trivial process creation time compared to
884 database startup overhead, but a few operating systems (Win32,
885 Solaris) might benefit from threading. Also explore the idea of
886 a single session using multiple threads to execute a statement faster.
888 </li><li>Add connection pooling
889 <p> It is unclear if this should be done inside the backend code or done
890 by something external like pgpool. The passing of file descriptors to
891 existing backends is one of the difficulties with a backend approach.
894 <h1><a name="section_19">Write-Ahead Log</a></h1>
897 <li>Eliminate need to write full pages to WAL before page modification [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?wal">wal</a>]
898 <p> Currently, to protect against partial disk page writes, we write
899 full page images to WAL before they are modified so we can correct any
900 partial page writes during recovery. These pages can also be
901 eliminated from point-in-time archive files.
904 <li>When off, write CRC to WAL and check file system blocks
906 <p> If CRC check fails during recovery, remember the page in case
907 a later CRC for that page properly matches.
909 </li><li>Write full pages during file system write and not when
910 the page is modified in the buffer cache
911 <p> This allows most full page writes to happen in the background
912 writer. It might cause problems for applying WAL on recovery
913 into a partially-written page, but later the full page will be
917 </li><li>Allow WAL traffic to be streamed to another server for stand-by
919 </li><li>Reduce WAL traffic so only modified values are written rather than
921 </li><li>Allow the pg_xlog directory location to be specified during initdb
922 with a symlink back to the /data location
923 </li><li>Allow WAL information to recover corrupted pg_controldata
924 </li><li>Find a way to reduce rotational delay when repeatedly writing
926 <p> Currently fsync of WAL requires the disk platter to perform a full
927 rotation to fsync again. One idea is to write the WAL to different
928 offsets that might reduce the rotational delay.
930 </li><li>Allow buffered WAL writes and fsync
931 <p> Instead of guaranteeing recovery of all committed transactions, this
932 would provide improved performance by delaying WAL writes and fsync
933 so an abrupt operating system restart might lose a few seconds of
934 committed transactions but still be consistent. We could perhaps
935 remove the 'fsync' parameter (which results in an an inconsistent
936 database) in favor of this capability.
938 </li><li>Allow WAL logging to be turned off for a table, but the table
939 might be dropped or truncated during crash recovery [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
940 <p> Allow tables to bypass WAL writes and just fsync() dirty pages on
941 commit. This should be implemented using ALTER TABLE, e.g. ALTER
942 TABLE PERSISTENCE [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo? DROP | TRUNCATE | DEFAULT "> DROP | TRUNCATE | DEFAULT </a>]. Tables using
943 non-default logging should not use referential integrity with
944 default-logging tables. A table without dirty buffers during a
945 crash could perhaps avoid the drop/truncate.
947 </li><li>Allow WAL logging to be turned off for a table, but the table would
948 avoid being truncated/dropped [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?walcontrol">walcontrol</a>]
949 <p> To do this, only a single writer can modify the table, and writes
950 must happen only on new pages so the new pages can be removed during
951 crash recovery. Readers can continue accessing the table. Such
952 tables probably cannot have indexes. One complexity is the handling
953 of indexes on TOAST tables.
956 <h1><a name="section_20">Optimizer / Executor</a></h1>
959 <li>Improve selectivity functions for geometric operators
960 </li><li>Allow ORDER BY ... LIMIT # to select high/low value without sort or
961 index using a sequential scan for highest/lowest values
962 <p> Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
963 all values to return the high/low value. Instead The idea is to do a
964 sequential scan to find the high/low value, thus avoiding the sort.
965 MIN/MAX already does this, but not for LIMIT > 1.
967 </li><li>Precompile SQL functions to avoid overhead
968 </li><li>Create utility to compute accurate random_page_cost value
969 </li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
970 </li><li>Have EXPLAIN ANALYZE highlight poor optimizer estimates
971 </li><li>Consider using hash buckets to do DISTINCT, rather than sorting
972 <p> This would be beneficial when there are few distinct values. This is
973 already used by GROUP BY.
975 </li><li>Log statements where the optimizer row estimates were dramatically
976 different from the number of rows actually found?
978 <h1><a name="section_21">Miscellaneous Performance</a></h1>
981 <li>Do async I/O for faster random read-ahead of data
982 <p> Async I/O allows multiple I/O requests to be sent to the disk with
983 results coming back asynchronously.
985 </li><li>Use mmap() rather than SYSV shared memory or to write WAL files?
986 <p> This would remove the requirement for SYSV SHM but would introduce
987 portability issues. Anonymous mmap (or mmap to /dev/zero) is required
988 to prevent I/O overhead.
990 </li><li>Consider mmap()'ing files into a backend?
991 <p> Doing I/O to large tables would consume a lot of address space or
992 require frequent mapping/unmapping. Extending the file also causes
993 mapping problems that might require mapping only individual pages,
994 leading to thousands of mappings. Another problem is that there is no
995 way to _prevent_ I/O to disk from the dirty shared buffers so changes
996 could hit disk before WAL is written.
998 </li><li>Add a script to ask system configuration questions and tune postgresql.conf
999 </li><li>Merge xmin/xmax/cmin/cmax back into three header fields
1000 <p> Before subtransactions, there used to be only three fields needed to
1001 store these four values. This was possible because only the current
1002 transaction looks at the cmin/cmax values. If the current transaction
1003 created and expired the row the fields stored where xmin (same as
1004 xmax), cmin, cmax, and if the transaction was expiring a row from a
1005 another transaction, the fields stored were xmin (cmin was not
1006 needed), xmax, and cmax. Such a system worked because a transaction
1007 could only see rows from another completed transaction. However,
1008 subtransactions can see rows from outer transactions, and once the
1009 subtransaction completes, the outer transaction continues, requiring
1010 the storage of all four fields. With subtransactions, an outer
1011 transaction can create a row, a subtransaction expire it, and when the
1012 subtransaction completes, the outer transaction still has to have
1013 proper visibility of the row's cmin, for example, for cursors.
1015 <p> One possible solution is to create a phantom cid which represents a
1016 cmin/cmax pair and is stored in local memory. Another idea is to
1017 store both cmin and cmax only in local memory.
1019 </li><li>Research storing disk pages with no alignment/padding
1021 <h1><a name="section_22">Source Code</a></h1>
1024 <li>Add use of 'const' for variables in source tree
1025 </li><li>Rename some /contrib modules from pg* to pg_*
1026 </li><li>Move some things from /contrib into main tree
1027 </li><li>Move some /contrib modules out to their own project sites
1028 </li><li>%Remove warnings created by -Wcast-align
1029 </li><li>Move platform-specific ps status display info from ps_status.c to ports
1030 </li><li>Add optional CRC checksum to heap and index pages
1031 </li><li>Improve documentation to build only interfaces (Marc)
1032 </li><li>Remove or relicense modules that are not under the BSD license, if possible
1033 </li><li>%Remove memory/file descriptor freeing before ereport(ERROR)
1034 </li><li>Acquire lock on a relation before building a relcache entry for it
1035 </li><li>%Promote debug_query_string into a server-side function current_query()
1036 </li><li>%Allow the identifier length to be increased via a configure option
1037 </li><li>Allow cross-compiling by generating the zic database on the target system
1038 </li><li>Improve NLS maintenance of libpgport messages linked onto applications
1039 </li><li>Allow ecpg to work with MSVC and BCC
1040 </li><li>Add xpath_array() to /contrib/xml2 to return results as an array
1041 </li><li>Allow building in directories containing spaces
1042 <p> This is probably not possible because 'gmake' and other compiler tools
1043 do not fully support quoting of paths with spaces.
1045 </li><li>-<em>Allow installing to directories containing spaces</em>
1046 <p> This is possible if proper quoting is added to the makefiles for the
1047 install targets. Because PostgreSQL supports relocatable installs, it
1048 is already possible to install into a directory that doesn't contain
1049 spaces and then copy the install to a directory with spaces.
1051 </li><li>Fix sgmltools so PDFs can be generated with bookmarks
1052 </li><li>-*%Clean up compiler warnings (especially with gcc version 4)*
1053 </li><li>Use UTF8 encoding for NLS messages so all server encodings can
1055 </li><li>Update Bonjour to work with newer cross-platform SDK
1056 </li><li>-<em>Remove BeOS and QNX-specific code</em>
1057 </li><li>Split out libpq pgpass and environment documentation sections to make
1058 it easier for non-developers to find
1061 <li>Remove configure.in check for link failure when cause is found
1062 </li><li>Remove readdir() errno patch when runtime/mingwex/dirent.c rev
1064 </li><li>Remove psql newline patch when we find out why mingw outputs an
1066 </li><li>Allow psql to use readline once non-US code pages work with
1068 </li><li>Re-enable timezone output on log_line_prefix '%t' when a
1069 shorter timezone string is available
1070 </li><li>Fix problem with shared memory on the Win32 Terminal Server
1071 </li><li>Improve signal handling,
1072 <a href="http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php">http://archives.postgresql.org/pgsql-patches/2005-06/msg00027.php</a>
1073 </li><li>Add long file support for binary pg_dump output
1074 <p> While Win32 supports 64-bit files, the MinGW API does not,
1075 meaning we have to build an fseeko replacement on top of the
1076 Win32 API, and we have to make sure MinGW handles it. Another
1077 option is to wait for the MinGW project to fix it, or use the
1078 code from the LibGW32C project as a guide.
1081 </li><li>Wire Protocol Changes
1083 <li>Allow dynamic character set handling
1084 </li><li>Add decoded type, length, precision
1085 </li><li>Use compression?
1086 </li><li>Update clients to use data types, typmod, <a href="http://schema.table.column">schema.table.column</a>/ names
1087 of result sets using new statement protocol
1092 <h2><a name="section_22_1">Developers who have claimed items are:</a></h2>
1094 <li>Alvaro is Alvaro Herrera <<a href="mailto:alvherre@dcc.uchile.cl">alvherre@dcc.uchile.cl</a>>
1095 </li><li>Andrew is Andrew Dunstan <<a href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>>
1096 </li><li>Bruce is Bruce Momjian <<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>> of Software Research Assoc.
1097 </li><li>Christopher is Christopher Kings-Lynne <<a href="mailto:chriskl@familyhealth.com.au">chriskl@familyhealth.com.au</a>> of
1098 Family Health Network
1099 </li><li>D'Arcy is D'Arcy J.M. Cain <<a href="mailto:darcy@druid.net">darcy@druid.net</a>> of The Cain Gang Ltd.
1100 </li><li>Fabien is Fabien Coelho <<a href="mailto:coelho@cri.ensmp.fr">coelho@cri.ensmp.fr</a>>
1101 </li><li>Gavin is Gavin Sherry <<a href="mailto:swm@linuxworld.com.au">swm@linuxworld.com.au</a>> of Alcove Systems Engineering
1102 </li><li>Greg is Greg Sabino Mullane <<a href="mailto:greg@turnstep.com">greg@turnstep.com</a>>
1103 </li><li>Jan is Jan Wieck <<a href="mailto:JanWieck@Yahoo.com">JanWieck@Yahoo.com</a>> of Afilias, Inc.
1104 </li><li>Joe is Joe Conway <<a href="mailto:mail@joeconway.com">mail@joeconway.com</a>>
1105 </li><li>Karel is Karel Zak <<a href="mailto:zakkr@zf.jcu.cz">zakkr@zf.jcu.cz</a>>
1106 </li><li>Magnus is Magnus Hagander <<a href="mailto:mha@sollentuna.net">mha@sollentuna.net</a>>
1107 </li><li>Marc is Marc Fournier <<a href="mailto:scrappy@hub.org">scrappy@hub.org</a>> of PostgreSQL, Inc.
1108 </li><li>Matthew T. O'Connor <<a href="mailto:matthew@zeut.net">matthew@zeut.net</a>>
1109 </li><li>Michael is Michael Meskes <<a href="mailto:meskes@postgresql.org">meskes@postgresql.org</a>> of Credativ
1110 </li><li>Neil is Neil Conway <<a href="mailto:neilc@samurai.com">neilc@samurai.com</a>>
1111 </li><li>Oleg is Oleg Bartunov <<a href="mailto:oleg@sai.msu.su">oleg@sai.msu.su</a>>
1112 </li><li>Peter is Peter Eisentraut <<a href="mailto:peter_e@gmx.net">peter_e@gmx.net</a>>
1113 </li><li>Philip is Philip Warner <<a href="mailto:pjw@rhyme.com.au">pjw@rhyme.com.au</a>> of Albatross Consulting Pty. Ltd.
1114 </li><li>Rod is Rod Taylor <<a href="mailto:pg@rbt.ca">pg@rbt.ca</a>>
1115 </li><li>Simon is Simon Riggs <<a href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>>
1116 </li><li>Stephan is Stephan Szabo <<a href="mailto:sszabo@megazone23.bigpanda.com">sszabo@megazone23.bigpanda.com</a>>
1117 </li><li>Tatsuo is Tatsuo Ishii <<a href="mailto:t-ishii@sra.co.jp">t-ishii@sra.co.jp</a>> of Software Research Assoc.
1118 </li><li>Teodor is Teodor Sigaev <<a href="mailto:teodor@sigaev.ru">teodor@sigaev.ru</a>>
1119 </li><li>Tom is Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> of Red Hat
1121 </li></ul></li></ul>