1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004
1005
1006
1007
1008
1009
1010
1011
1012
1013
1014
1015
1016
1017
1018
1019
1020
1021
1022
1023
1024
1025
1026
1027
1028
1029
1030
1031
1032
1033
1034
1035
1036
1037
1038
1039
1040
1041
1042
1043
1044
1045
1046
1047
1048
1049
1050
1051
1052
1053
1054
1055
1056
1057
1058
1059
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>PostgreSQL TODO List</title>
<meta name="generator" content="HTML::TextToHTML v2.25"/>
</head>
<body bgcolor="#FFFFFF" text="#000000" link="#FF0000" vlink="#A00000" alink="#0000FF">
<h1><a name="section_1">PostgreSQL TODO List</a></h1>
<p>Current maintainer: Bruce Momjian (<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>)<br/>
Last updated: Tue Aug 23 19:51:09 EDT 2005
</p>
<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>.
</p>
<p><strong>A hyphen, "-", marks changes that will appear in the upcoming 8.1 release.</strong>
</p>
<p>Bracketed items, "[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]", have more detail.
</p>
<p>This list contains all known PostgreSQL bugs and feature requests. If<br/>
you would like to work on an item, please read the Developer's FAQ<br/>
first.
</p>
<h1><a name="section_2">Administration</a></h1>
<ul>
<li>Remove behavior of postmaster -o after making postmaster/postgres
flags unique
</li><li>-<em>Allow limits on per-db/role connections</em>
</li><li>Allow pooled connections to list all prepared queries
<p> This would allow an application inheriting a pooled connection to know
the queries prepared in the current session.
</p>
</li><li>Allow major upgrades without dump/reload, perhaps using pg_upgrade
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pg_upgrade">pg_upgrade</a>]
</li><li>Check for unreferenced table files created by transactions that were
in-progress when the server terminated abruptly
</li><li>Allow administrators to safely terminate individual sessions either
via an SQL function or SIGTERM
<p> Currently SIGTERM of a backend can lead to lock table corruption.
</p>
</li><li>-<em>Prevent dropping user that still owns objects, or auto-drop the objects</em>
</li><li>Set proper permissions on non-system schemas during db creation
<p> Currently all schemas are owned by the super-user because they are
copied from the template1 database.
</p>
</li><li>-<em>Add the client IP address and port to pg_stat_activity</em>
</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
</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>
</li><li>Configuration files
<ul>
<li>Add "include file" functionality in postgresql.conf
</li><li>Allow postgresql.conf values to be set so they can not be changed
by the user
</li><li>Allow commenting of variables in postgresql.conf to restore them
to defaults
</li><li>Allow pg_hba.conf settings to be controlled via SQL
<p> This would add a function to load the SQL table from
pg_hba.conf, and one to writes its contents to the flat file.
The table should have a line number that is a float so rows
can be inserted between existing rows, e.g. row 2.5 goes
between row 2 and row 3.
</p>
</li><li>Allow postgresql.conf file values to be changed via an SQL
API, perhaps using SET GLOBAL
</li><li>Allow the server to be stopped/restarted via an SQL API
</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>
<ul>
<li>Add a GUC variable to control the tablespace for temporary objects
and sort files
<p> It could start with a random tablespace from a supplied list and
cycle through the list.
</p>
</li><li>Allow WAL replay of CREATE TABLESPACE to work when the directory
structure on the recovery computer is different from the original
</li><li>Allow per-tablespace quotas
</li></ul>
</li></ul>
</li><li>Point-In-Time Recovery (PITR)
<ul>
<li>Allow point-in-time recovery to archive partially filled
write-ahead logs [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p> Currently only full WAL files are archived. This means that the
most recent transactions aren't available for recovery in case
of a disk failure. This could be triggered by a user command or
a timer.
</p>
</li><li>Automatically force archiving of partially-filled WAL files when
pg_stop_backup() is called or the server is stopped
<p> Doing this will allow administrators to know more easily when
the archive contins all the files needed for point-in-time
recovery.
</p>
</li><li>Create dump tool for write-ahead logs for use in determining
transaction id for point-in-time recovery
</li><li>Allow a warm standby system to also allow read-only queries
[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?pitr">pitr</a>]
<p> This is useful for checking PITR recovery.
</p>
</li><li>Allow the PITR process to be debugged and data examined
</li></ul>
</li></ul>
<h1><a name="section_3">Monitoring</a></h1>
<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>
</li><li>Add ability to monitor the use of temporary sort files
</li><li>-<em>Add session start time and last statement time to pg_stat_activity</em>
</li><li>-<em>Add a function that returns the start time of the postmaster</em>
</li><li>Allow server logs to be remotely read and removed using SQL commands
</li></ul>
<h1><a name="section_4">Data Types</a></h1>
<ul>
<li>Remove Money type, add money formatting for decimal type
</li><li>Change NUMERIC to enforce the maximum precision, and increase it
</li><li>Add NUMERIC division operator that doesn't round?
<p> Currently NUMERIC _rounds_ the result to the specified precision.
This means division can return a result that multiplied by the
divisor is greater than the dividend, e.g. this returns a value > 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>
<li>Have sequence dependency track use of DEFAULT sequences,
seqname.nextval?
</li><li>Disallow changing default expression of a SERIAL column?
</li><li>Fix data types where equality comparison isn't intuitive, e.g. box
</li><li>Prevent INET cast to CIDR if the unmasked bits are not zero, or
zero the bits
</li><li>Prevent INET cast to CIDR from droping netmask, SELECT '<a href="telnet://1.1.1.1">1.1.1.1</a>'::inet::cidr
</li><li>Allow INET + INT4 to increment the host part of the address, or
throw an error on overflow
</li><li>Add 'tid != tid ' operator for use in corruption recovery
</li><li>Dates and Times
<ul>
<li>Allow infinite dates just like infinite timestamps
</li><li>Add a GUC variable to allow output of interval values in ISO8601
format
</li><li>Merge hardwired timezone names with the TZ database; allow either
kind everywhere a TZ name is currently taken
</li><li>Allow customization of the known set of TZ names (generalize the
present australian_timezones hack)
</li><li>Allow TIMESTAMP WITH TIME ZONE to store the original timezone
information, either zone name or offset from UTC [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?timezone">timezone</a>]
<p> If the TIMESTAMP value is stored with a time zone name, interval
computations should adjust based on the time zone rules.
</p>
</li><li>Add ISO INTERVAL handling
<ul>
<li>Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO
SECOND
</li><li>Add support for year-month syntax, INTERVAL '50-6' YEAR TO MONTH
</li><li>For syntax that isn't uniquely ISO or PG syntax, like '1:30' or
'1', treat as ISO if there is a range specification clause,
and as PG if there no clause is present, e.g. interpret
<p> '1:30' MINUTE TO SECOND as '1 minute 30 seconds', and
interpret '1:30' as '1 hour, 30 minutes'
<li>Interpret INTERVAL '1 year' MONTH as CAST (INTERVAL '1 year' AS
INTERVAL MONTH), and this should return '12 months'
</li><li>Round or truncate values to the requested precision, e.g.
INTERVAL '11 months' AS YEAR should return one or zero
</li><li>Support precision, CREATE TABLE foo (a INTERVAL MONTH(3))
</li></ul>
</p></ul>
</li><li>Arrays
<ul>
<li>Allow NULLs in arrays
</li><li>Allow MIN()/MAX() on arrays
</li><li>Delay resolution of array expression's data type so assignment
coercion can be performed on empty array expressions
</li><li>Modify array literal representation to handle array index lower bound
of other than one
</li></ul>
</li><li>Binary Data
<ul>
<li>Improve vacuum of large objects, like /contrib/vacuumlo?
</li><li>Add security checking for large objects
<p> Currently large objects entries do not have owners. Permissions can
only be set at the pg_largeobject table level.
</p>
</li><li>Auto-delete large objects when referencing row is deleted
</li><li>Allow read/write into TOAST values like large objects
<p> This requires the TOAST column to be stored EXTERNAL.
</p>
</li></ul>
</li></ul>
<h1><a name="section_5">Functions</a></h1>
<ul>
<li>-<em>Add function to return compressed length of TOAST data values</em>
</li><li>Allow INET subnet tests using non-constants to be indexed
</li><li>Add transaction_timestamp(), statement_timestamp(), clock_timestamp()
functionality
<p> Current CURRENT_TIMESTAMP returns the start time of the current
transaction, and gettimeofday() returns the wallclock time. This will
make time reporting more consistent and will allow reporting of
the statement start time.
</p>
</li><li>Add pg_get_acldef(), pg_get_typedefault(), and pg_get_attrdef()
</li><li>Allow to_char() to print localized month names
</li><li>Allow functions to have a schema search path specified at creation time
</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') => 65
</li><li>to_char(INTERVAL '43 hours 20 minutes', 'MI' ) => 2600
</li><li>to_char(INTERVAL '43 hours 20 minutes', 'WK:DD:HR:MI') => 0:1:19:20
</li><li>to_char(INTERVAL '3 years 5 months','MM') => 41
</li></ul>
</li><li>-<em>Prevent to_char() on interval from returning meaningless values</em>
<p> For example, to_char('1 month', 'mon') is meaningless. Basically,
most date-related parameters to to_char() are meaningless for
intervals because interval is not anchored to a date.
</p>
</li></ul>
<h1><a name="section_6">Multi-Language Support</a></h1>
<ul>
<li>Add NCHAR (as distinguished from ordinary varchar),
</li><li>Allow locale to be set at database creation
<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.
</p>
</li><li>Allow encoding on a per-column basis
<p> Right now only one encoding is allowed per database.
</p>
</li><li>Support multiple simultaneous character sets, per SQL92
</li><li>Improve UTF8 combined character handling?
</li><li>Add octet_length_server() and octet_length_client()
</li><li>Make octet_length_client() the same as octet_length()?
</li><li>Fix problems with wrong runtime encoding conversion for NLS message files
</li></ul>
<h1><a name="section_7">Views / Rules</a></h1>
<ul>
<li>Automatically create rules on views so they are updateable, per SQL99
<p> We can only auto-create rules for simple views. For more complex
cases users will still have to write rules.
</p>
</li><li>Add the functionality for WITH CHECK OPTION clause of CREATE VIEW
</li><li>Allow NOTIFY in rules involving conditionals
</li><li>Have views on temporary tables exist in the temporary namespace
</li><li>Allow temporary views on non-temporary tables
</li><li>Allow RULE recompilation
</li></ul>
<h1><a name="section_8">SQL Commands</a></h1>
<ul>
<li>-<em>Add BETWEEN SYMMETRIC/ASYMMETRIC</em>
</li><li>Change LIMIT/OFFSET and FETCH/MOVE to use int8
</li><li>-<em>Add E'' escape string marker so eventually ordinary strings can treat</em>
backslashes literally, for portability
</li><li>-<em>Allow additional tables to be specified in DELETE for joins</em>
<p> UPDATE already allows this (UPDATE...FROM) but we need similar
functionality in DELETE. It's been agreed that the keyword should
be USING, to avoid anything as confusing as DELETE FROM a FROM b.
</p>
</li><li>Add CORRESPONDING BY to UNION/INTERSECT/EXCEPT
</li><li>-<em>Allow REINDEX to rebuild all database indexes</em>
</li><li>Add ROLLUP, CUBE, GROUPING SETS options to GROUP BY
</li><li>Allow SET CONSTRAINTS to be qualified by schema/table name
</li><li>Allow TRUNCATE ... CASCADE/RESTRICT
</li><li>Add a separate TRUNCATE permission
<p> Currently only the owner can TRUNCATE a table because triggers are not
called, and the table is locked in exclusive mode.
</p>
</li><li>Allow PREPARE of cursors
</li><li>Allow PREPARE to automatically determine parameter types based on the SQL
statement
</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>
</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.
</p>
</li><li>Add a GUC variable to warn about non-standard SQL usage in queries
</li><li>Add MERGE command that does UPDATE/DELETE, or on failure, INSERT (rules,
triggers?)
</li><li>Add NOVICE output level for helpful messages like automatic sequence/index
creation
</li><li>Add COMMENT ON for all cluster global objects (roles, databases
and tablespaces)
</li><li>-<em>Add an option to automatically use savepoints for each statement in a</em>
multi-statement transaction.
<p> When enabled, this would allow errors in multi-statement transactions
to be automatically ignored.
</p>
</li><li>Make row-wise comparisons work per SQL spec
</li><li>Add RESET CONNECTION command to reset all session state
<p> This would include resetting of all variables (RESET ALL), dropping of
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
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
notify the protocol when a RESET CONNECTION command is used.
</p>
</li><li>Add GUC to issue notice about queries that use unjoined tables
</li><li>Allow EXPLAIN to identify tables that were skipped because of
constraint_exclusion
</li><li>Allow EXPLAIN output to be more easily processed by scripts
</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?
</li><li>Currently the system uses the operating system COPY command to
create a new database. Add ON COMMIT capability to CREATE TABLE AS
SELECT
</li></ul>
</li><li>UPDATE
<ul>
<li>Allow UPDATE to handle complex aggregates [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?update">update</a>]?
</li><li>Allow an alias to be provided for the target table in
UPDATE/DELETE
<p> This is not SQL-spec but many DBMSs allow it.
</p>
</li><li>Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple
columns
</li><li>-<em>Allow FOR UPDATE queries to do NOWAIT locks</em>
</li></ul>
</li><li>ALTER
<ul>
<li>Have ALTER TABLE RENAME rename SERIAL sequence names
</li><li>Add ALTER DOMAIN TYPE
</li><li>Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
</li><li>Allow ALTER TABLE to change constraint deferrability and actions
</li><li>Disallow dropping of an inherited constraint
</li><li>-<em>Allow objects to be moved to different schemas</em>
</li><li>Allow ALTER TABLESPACE to move to different directories
</li><li>Allow databases to be moved to different tablespaces
</li><li>Allow moving system tables to other tablespaces, where possible
<p> Currently non-global system tables must be in the default database
tablespace. Global system tables can never be moved.
</p>
</li><li>Prevent child tables from altering constraints like CHECK that were
inherited from the parent table
</li></ul>
</li><li>CLUSTER
<ul>
<li>Automatically maintain clustering on a table
<p> This might require some background daemon to maintain clustering
during periods of low usage. It might also require tables to be only
paritally filled for easier reorganization. Another idea would
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.
</p>
</li><li>Add default clustering to system tables
<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>
</li><li>-<em>Allow COPY to understand \x as a hex byte</em>
</li><li>Have COPY return the number of rows loaded/unloaded?
</li><li>-<em>Allow COPY to optionally include column headings in the first line</em>
</li><li>-<em>Allow COPY FROM ... CSV to interpret newlines and carriage</em>
returns in data
</li></ul>
</li><li>GRANT/REVOKE
<ul>
<li>Allow column-level privileges
</li><li>Allow GRANT/REVOKE permissions to be applied to all schema objects
with one command
<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>
<ul>
<li>Allow GRANT/REVOKE permissions to be inherited by objects based on
schema permissions
</li></ul>
</li></ul>
</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
cursor?
</li><li>Allow pooled connections to list all open WITH HOLD cursors
<p> Because WITH HOLD cursors exist outside transactions, this allows
them to be listed so they can be closed.
</p>
</li></ul>
</li><li>INSERT
<ul>
<li>Allow INSERT/UPDATE of the system-generated oid value for a row
</li><li>Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..)
</li><li>Allow INSERT/UPDATE ... RETURNING new.col or old.col
<p> This is useful for returning the auto-generated key for an INSERT.
One complication is how to handle rules that run as part of
the insert.
</p>
</li></ul>
</li><li>SHOW/SET
<ul>
<li>-<em>Have SHOW ALL show descriptions for server-side variables</em>
</li><li>Add SET PERFORMANCE_TIPS option to suggest INDEX, VACUUM, VACUUM
ANALYZE, and CLUSTER
</li><li>Add SET PATH for schemas?
<p> This is basically the same as SET search_path.
</p>
</li></ul>
</li><li>Server-Side Languages
<ul>
<li>-<em>Allow PL/PgSQL's RAISE function to take expressions</em>
<p> Currently only constants are supported.
</p>
</li><li>-<em>Change PL/PgSQL to use palloc() instead of malloc()</em>
</li><li>Handle references to temporary tables that are created, destroyed,
then recreated during a session, and EXECUTE is not used
<p> This requires the cached PL/PgSQL byte code to be invalidated when
an object referenced in the function is changed.
</p>
</li><li>Fix PL/pgSQL RENAME to work on variables other than OLD/NEW
</li><li>Allow function parameters to be passed by name,
get_employee_salary(emp_id => 12345, tax_year => 2001)
</li><li>Add Oracle-style packages
</li><li>Add table function support to pltcl, plperl, plpython?
</li><li>Allow PL/pgSQL to name columns by ordinal position, e.g. rec.(3)
</li><li>-<em>Allow PL/pgSQL EXECUTE query_var INTO record_var;</em>
</li><li>Add capability to create and call PROCEDURES
</li><li>Allow PL/pgSQL to handle %TYPE arrays, e.g. tab.col%TYPE[<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?"></a>]
</li><li>Add MOVE to PL/pgSQL
</li><li>Pass arrays natively instead of as text between plperl and postgres
</li><li>Add support for polymorphic arguments and return types to plperl
</li></ul>
</li></ul>
<h1><a name="section_9">Clients</a></h1>
<ul>
<li>Add a libpq function to support Parse/DescribeStatement capability
</li><li>Prevent libpq's PQfnumber() from lowercasing the column name?
</li><li>Allow libpq to access SQLSTATE so pg_ctl can test for connection failure
<p> This would be used for checking if the server is up.
</p>
</li><li>Add PQescapeIdentifier() to libpq
</li><li>Have initdb set DateStyle based on locale?
</li><li>Have pg_ctl look at PGHOST in case it is a socket directory?
</li><li>Add a schema option to createlang
</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.
</p>
</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>
</li><li>Fix psql's display of schema information (Neil)
</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
</li><li>Improve psql's handling of multi-line queries
</li></ul>
</li><li>pg_dump
<ul>
<li>Have pg_dump use multi-statement transactions for INSERT dumps
</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>]
</li><li>Add dumping of comments on composite type columns
</li><li>Add dumping of comments on index columns
</li><li>Replace crude DELETE FROM method of pg_dumpall --clean for
cleaning of roles with separate DROP commands
</li><li>-<em>Add dumping and restoring of LOB comments</em>
</li><li>Stop dumping CASCADE on DROP TYPE commands in clean mode
</li><li>Add full object name to the tag field. eg. for operators we need
'=(integer, integer)', instead of just '='.
</li><li>Add pg_dumpall custom format dumps.
<p> This is probably best done by combining pg_dump and pg_dumpall
into a single binary.
</p>
</li><li>Add CSV output format
</li><li>Update pg_dump and psql to use the new COPY libpq API (Christopher)
</li><li>Remove unnecessary abstractions in pg_dump source code
</li></ul>
</li><li>ecpg
<ul>
<li>Docs
<p> Document differences between ecpg and the SQL standard and
information about the Informix-compatibility module.
</p>
</li><li>Solve cardinality > 1 for input descriptors / variables?
</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
</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
</li><li>Make SET CONNECTION thread-aware, non-standard?
</li><li>Allow multidimensional arrays
</li><li>Add internationalized message strings
</li></ul>
</li></ul>
<h1><a name="section_10">Referential Integrity</a></h1>
<ul>
<li>Add MATCH PARTIAL referential integrity
</li><li>Add deferred trigger queue file
<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.
</p>
</li><li>-<em>Implement shared row locks and use them in RI triggers</em>
</li><li>Change foreign key constraint for array -> element to mean element
in array?
</li><li>Allow DEFERRABLE UNIQUE constraints?
</li><li>-<em>Allow triggers to be disabled [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?trigger">trigger</a>]</em>
</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 ...
TRIGGER requires a table lock so it is not idea for this usage.
</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
</li><li>Support triggers on columns (Greg Sabino Mullane)
</li><li>Remove CREATE CONSTRAINT TRIGGER
<p> This was used in older releases to dump referential integrity
constraints.
</p>
</li><li>Enforce referential integrity for system tables
</li><li>Allow AFTER triggers on system tables
<p> System tables are modified in many places in the backend without going
through the executor and therefore not causing triggers to fire. To
complete this item, the functions that modify system tables will have
to fire triggers.
</p>
</li></ul>
<h1><a name="section_11">Dependency Checking</a></h1>
<ul>
<li>Flush cached query plans when the dependent objects change
</li><li>Track dependencies in function bodies and recompile/invalidate
</li></ul>
<h1><a name="section_12">Exotic Features</a></h1>
<ul>
<li>Add SQL99 WITH clause to SELECT
</li><li>Add SQL99 WITH RECURSIVE to SELECT
</li><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 queries across databases or servers with transaction
semantics
<p> This can be done using dblink and two-phase commit.
</p>
</li><li>-<em>Add two-phase commit</em>
</li><li>Add the features of packages
<ul>
<li>Make private objects accessable 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></ul>
<h1><a name="section_13">Indexes</a></h1>
<ul>
<li>Allow inherited tables to inherit index, UNIQUE constraint, and primary
key, foreign key
</li><li>UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
inherited table: INSERT INTO inherit_table (unique_index_col) VALUES
(dup) should fail
<p> The main difficulty with this item is the problem of creating an index
that can span more than one table.
</p>
</li><li>Allow SELECT ... FOR UPDATE on inherited tables
</li><li>-<em>Prevent inherited tables from expanding temporary subtables of other</em>
sessions
</li><li>Add UNIQUE capability to non-btree indexes
</li><li>-<em>Use indexes for MIN() and MAX()</em>
<p> MIN/MAX queries can already be rewritten as SELECT col FROM tab ORDER
BY col {DESC} LIMIT 1. Completing this item involves doing this
transformation automatically.
</p>
</li><li>-<em>Use index to restrict rows returned by multi-key index when used with</em>
non-consecutive keys to reduce heap accesses
<p> For an index on col1,col2,col3, and a WHERE clause of col1 = 5 and
col3 = 9, spin though the index checking for col1 and col3 matches,
rather than just col1; also called skip-scanning.
</p>
</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>Fetch heap pages matching index entries in sequential order
<p> Rather than randomly accessing heap pages based on index entries, mark
heap pages needing access in a bitmap and do the lookups in sequential
order. Another method would be to sort heap ctids matching the index
before accessing the heap rows.
</p>
</li><li>-<em>Allow non-bitmap indexes to be combined by creating bitmaps in memory</em>
<p> This feature allows separate indexes to be ANDed or ORed together. This
is particularly useful for data warehousing applications that need to
query the database in an many permutations. This feature scans an index
and creates an in-memory bitmap, and allows that bitmap to be combined
with other bitmap created in a similar way. The bitmap can either index
all TIDs, or be lossy, meaning it records just page numbers and each
page tuple has to be checked for validity in a separate pass.
</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.
</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
</li><li>Add fillfactor to control reserved free space during index creation
</li><li>Allow the creation of indexes with mixed ascending/descending specifiers
</li><li>-<em>Fix incorrect rtree results due to wrong assumptions about "over"</em>
operator semantics
</li><li>Allow constraint_exclusion to work for UNIONs like it does for
inheritance, and allow it to work for UPDATE and DELETE queries
</li><li>GIST
<ul>
<li>Add more GIST index support for geometric data types
</li><li>-<em>Add concurrency to GIST</em>
</li><li>Allow GIST indexes to create certain complex index types, like
digital trees (see Aoki)
</li></ul>
</li><li>Hash
<ul>
<li>Pack hash index buckets onto disk pages more efficiently
<p> Currently no only one hash bucket can be stored on a page. Ideally
several hash buckets could be stored on a single page and greater
granularity used for the hash algorithm.
</p>
</li><li>Consider sorting hash buckets so entries can be found using a
binary search, rather than a linear scan
</li><li>In hash indexes, consider storing the hash value with or instead
of the key itself
</li></ul>
</li></ul>
<h1><a name="section_14">Fsync</a></h1>
<ul>
<li>Improve commit_delay handling to reduce fsync()
</li><li>Determine optimal fdatasync/fsync, O_SYNC/O_DSYNC options
</li><li>-<em>Allow multiple blocks to be written to WAL with one write()</em>
</li><li>Add an option to sync() before fsync()'ing checkpoint files
</li><li>Add program to test if fsync has a delay compared to non-fsync
</li></ul>
<h1><a name="section_15">Cache Usage</a></h1>
<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>-<em>Consider use of open/fcntl(O_DIRECT) to minimize OS caching,</em>
for WAL writes
<p> O_DIRECT doesn't have the same media write guarantees as fsync, so it
is in addition to the fsync method, not in place of it.
</p>
</li><li>-<em>Cache last known per-tuple offsets to speed long tuple access</em>
</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.
</p>
</li><li>Allow data to be pulled directly from indexes
<p> Currently indexes do not have enough tuple visibility information
to allow data to be pulled from the index without also accessing
the heap. One way to allow this is to set a bit to index tuples
to indicate if a tuple is currently visible to all transactions
when the first valid heap lookup happens. This bit would have to
be cleared when a heap tuple is expired.
</p>
</li><li>Consider automatic caching of queries at various levels:
<ul>
<li>Parsed query tree
</li><li>Query execute plan
</li><li>Query results
</li></ul>
</li><li>-<em>Allow the size of the buffer cache used by temporary objects to be</em>
specified as a GUC variable
<p> Larger local buffer cache sizes requires more efficient handling of
local cache lookups.
</p>
</li><li>Improve the background writer
<p> Allow the background writer to more efficiently write dirty buffers
from the end of the LRU cache and use a clock sweep algorithm to
write other dirty buffers to reduced checkpoint I/O
</p>
</li><li>Allow sequential scans to take advantage of other concurrent
sequentiqal scans, also called "Synchronised Scanning"
<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.
</p>
</li></ul>
<h1><a name="section_16">Vacuum</a></h1>
<ul>
<li>Improve speed with indexes
<p> For large table adjustements during vacuum, it is faster to reindex
rather than update the index.
</p>
</li><li>Reduce lock time by moving tuples with read lock, then write
lock and truncate table
<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.
</p>
</li><li>-<em>Add a warning when the free space map is too small</em>
</li><li>Maintain a map of recently-expired rows
<p> This allows vacuum to target specific pages for possible free space
without requiring a sequential scan.
</p>
</li><li>Auto-fill the free space map by scanning the buffer cache or by
checking pages written by the background writer
</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.
</p>
</li><li>Add system view to show free space map contents
</li><li>Auto-vacuum
<ul>
<li>-<em>Move into the backend code</em>
</li><li>Use free-space map information to guide refilling
</li><li>Do VACUUM FULL if table is nearly empty?
</li><li>Improve xid wraparound detection by recording per-table rather
than per-database
</li></ul>
</li></ul>
<h1><a name="section_17">Locking</a></h1>
<ul>
<li>-<em>Make locking of shared data structures more fine-grained</em>
<p> This requires that more locks be acquired but this would reduce lock
contention, improving concurrency.
</p>
</li><li>Add code to detect an SMP machine and handle spinlocks accordingly
from distributted.net, <a href="http://www1.distributed.net/source">http://www1.distributed.net/source</a>,
in client/common/cpucheck.cpp
<p> On SMP machines, it is possible that locks might be released shortly,
while on non-SMP machines, the backend should sleep so the process
holding the lock can complete and release it.
</p>
</li><li>-<em>Improve SMP performance on i386 machines</em>
<p> i386-based SMP machines can generate excessive context switching
caused by lock failure in high concurrency situations. This may be
caused by CPU cache line invalidation inefficiencies.
</p>
</li><li>Research use of sched_yield() for spinlock acquisition failure
</li><li>Fix priority ordering of read and write light-weight locks (Neil)
</li></ul>
<h1><a name="section_18">Startup Time Improvements</a></h1>
<ul>
<li>Experiment with multi-threaded backend [<a href="http://momjian.postgresql.org/cgi-bin/pgtodo?thread">thread</a>]
<p> This would prevent the overhead associated with process creation. Most
operating systems have trivial process creation time compared to
database startup overhead, but a few operating systems (WIn32,
Solaris) might benefit from threading. Also explore the idea of
a single session using multiple threads to execute a query faster.
</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>
<h1><a name="section_19">Write-Ahead Log</a></h1>
<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>]
<p> Currently, to protect against partial disk page writes, we write
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>
<ul>
<li>-Add ability to turn off full page writes
</li><li>When off, write CRC to WAL and check file system blocks
on recovery
<p> If CRC check fails during recovery, remember the page in case
a later CRC for that page properly matches.
</p>
</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
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.
</p>
</li></ul>
</li><li>Reduce WAL traffic so only modified values are written rather than
entire rows?
</li><li>Add WAL index reliability improvement to non-btree indexes
</li><li>Allow the pg_xlog directory location to be specified during initdb
with a symlink back to the /data location
</li><li>Allow WAL information to recover corrupted pg_controldata
</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.
</p>
</li><li>-<em>Eliminate WAL logging for CREATE TABLE AS when not doing WAL archiving</em>
</li><li>-<em>Change WAL to use 32-bit CRC, for performance reasons</em>
</li></ul>
<h1><a name="section_20">Optimizer / Executor</a></h1>
<ul>
<li>Add missing optimizer selectivities for date, r-tree, etc
</li><li>Allow ORDER BY ... LIMIT # to select high/low value without sort or
index using a sequential scan for highest/lowest values
<p> Right now, if no index exists, ORDER BY ... LIMIT # requires we sort
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.
MIN/MAX already does this, but not for LIMIT > 1.
</p>
</li><li>Precompile SQL functions to avoid overhead
</li><li>Create utility to compute accurate random_page_cost value
</li><li>Improve ability to display optimizer analysis using OPTIMIZER_DEBUG
</li><li>Have EXPLAIN ANALYZE highlight poor optimizer estimates
</li><li>-<em>Use CHECK constraints to influence optimizer decisions</em>
<p> CHECK constraints contain information about the distribution of values
within the table. This is also useful for implementing subtables where
a tables content is distributed across several subtables.
</p>
</li><li>Consider using hash buckets to do DISTINCT, rather than sorting
<p> This would be beneficial when there are few distinct values.
</p>
</li><li>ANALYZE should record a pg_statistic entry for an all-NULL column
</li><li>Log queries where the optimizer row estimates were dramatically
different from the number of rows actually found?
</li></ul>
<h1><a name="section_21">Miscellaneous Performance</a></h1>
<ul>
<li>Do async I/O for faster random read-ahead of data
<p> Async I/O allows multiple I/O requests to be sent to the disk with
results coming back asynchronously.
</p>
</li><li>Use mmap() rather than SYSV shared memory or to write WAL files?
<p> This would remove the requirement for SYSV SHM but would introduce
portability issues. Anonymous mmap (or mmap to /dev/zero) is required
to prevent I/O overhead.
</p>
</li><li>Consider mmap()'ing files into a backend?
<p> Doing I/O to large tables would consume a lot of address space or
require frequent mapping/unmapping. Extending the file also causes
mapping problems that might require mapping only individual pages,
leading to thousands of mappings. Another problem is that there is no
way to _prevent_ I/O to disk from the dirty shared buffers so changes
could hit disk before WAL is written.
</p>
</li><li>Add a script to ask system configuration questions and tune postgresql.conf
</li><li>Use a phantom command counter for nested subtransactions to reduce
per-tuple overhead
</li><li>Research storing disk pages with no alignment/padding
</li></ul>
<h1><a name="section_22">Source Code</a></h1>
<ul>
<li>Add use of 'const' for variables in source tree
</li><li>Rename some /contrib modules from pg* to pg_*
</li><li>Move some things from /contrib into main tree
</li><li>Move some /contrib modules out to their own project sites
</li><li>Remove warnings created by -Wcast-align
</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
</li><li>Remove memory/file descriptor freeing before ereport(ERROR)
</li><li>Acquire lock on a relation before building a relcache entry for it
</li><li>Promote debug_query_string into a server-side function current_query()
</li><li>Allow the identifier length to be increased via a configure option
</li><li>Remove Win32 rename/unlink looping if unnecessary
</li><li>-<em>Remove kerberos4 from source tree</em>
</li><li>Allow cross-compiling by generating the zic database on the target system
</li><li>Improve NLS maintenace of libpgport messages linked onto applications
</li><li>Allow ecpg to work with MSVC and BCC
</li><li>-<em>Make src/port/snprintf.c thread-safe</em>
</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>
</li><li>Allow installing to directories containing spaces
<p> This is possible if proper quoting is added to the makefiles for the
install targets. Because PostgreSQL supports relocatable installs, it
is already possible to install into a directory that doesn't contain
spaces and then copy the install to a directory with spaces.
</p>
</li><li>Fix cross-compiling of time zone database via 'zic'
</li><li>Fix sgmltools so PDFs can be generated with bookmarks
</li><li>-<em>Add C code on Unix to copy directories for use in creating new databases</em>
</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>Improve dlerror() reporting string
</li><li>Fix problem with shared memory on the Win32 Terminal Server
</li><li>Add support for Unicode
<p> To fix this, the data needs to be converted to/from UTF16/UTF8
so the Win32 wcscoll() can be used, and perhaps other functions
like towupper(). However, UTF8 already works with normal
locales but provides no ordering or character set classes.
</p>
</li></ul>
</li><li>Wire Protocol Changes
<ul>
<li>Allow dynamic character set handling
</li><li>Add decoded type, length, precision
</li><li>Use compression?
</li><li>Update clients to use data types, typmod, <a href="http://schema.table.column">schema.table.column</a>/ names
of result sets using new query protocol
</li></ul>
</li></ul>
<hr/>
<h2><a name="section_22_1">Developers who have claimed items are:</a></h2>
<ul>
<li>Alvaro is Alvaro Herrera <<a href="mailto:alvherre@dcc.uchile.cl">alvherre@dcc.uchile.cl</a>>
</li><li>Andrew is Andrew Dunstan <<a href="mailto:andrew@dunslane.net">andrew@dunslane.net</a>>
</li><li>Bruce is Bruce Momjian <<a href="mailto:pgman@candle.pha.pa.us">pgman@candle.pha.pa.us</a>> of Software Research Assoc.
</li><li>Christopher is Christopher Kings-Lynne <<a href="mailto:chriskl@familyhealth.com.au">chriskl@familyhealth.com.au</a>> of
Family Health Network
</li><li>Claudio is Claudio Natoli <<a href="mailto:claudio.natoli@memetrics.com">claudio.natoli@memetrics.com</a>>
</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.
</li><li>Fabien is Fabien Coelho <<a href="mailto:coelho@cri.ensmp.fr">coelho@cri.ensmp.fr</a>>
</li><li>Gavin is Gavin Sherry <<a href="mailto:swm@linuxworld.com.au">swm@linuxworld.com.au</a>> of Alcove Systems Engineering
</li><li>Greg is Greg Sabino Mullane <<a href="mailto:greg@turnstep.com">greg@turnstep.com</a>>
</li><li>Hiroshi is Hiroshi Inoue <<a href="mailto:Inoue@tpf.co.jp">Inoue@tpf.co.jp</a>>
</li><li>Jan is Jan Wieck <<a href="mailto:JanWieck@Yahoo.com">JanWieck@Yahoo.com</a>> of Afilias, Inc.
</li><li>Joe is Joe Conway <<a href="mailto:mail@joeconway.com">mail@joeconway.com</a>>
</li><li>Karel is Karel Zak <<a href="mailto:zakkr@zf.jcu.cz">zakkr@zf.jcu.cz</a>>
</li><li>Magnus is Magnus Hagander <<a href="mailto:mha@sollentuna.net">mha@sollentuna.net</a>>
</li><li>Marc is Marc Fournier <<a href="mailto:scrappy@hub.org">scrappy@hub.org</a>> of PostgreSQL, Inc.
</li><li>Matthew T. O'Connor <<a href="mailto:matthew@zeut.net">matthew@zeut.net</a>>
</li><li>Michael is Michael Meskes <<a href="mailto:meskes@postgresql.org">meskes@postgresql.org</a>> of Credativ
</li><li>Neil is Neil Conway <<a href="mailto:neilc@samurai.com">neilc@samurai.com</a>>
</li><li>Oleg is Oleg Bartunov <<a href="mailto:oleg@sai.msu.su">oleg@sai.msu.su</a>>
</li><li>Peter is Peter Eisentraut <<a href="mailto:peter_e@gmx.net">peter_e@gmx.net</a>>
</li><li>Philip is Philip Warner <<a href="mailto:pjw@rhyme.com.au">pjw@rhyme.com.au</a>> of Albatross Consulting Pty. Ltd.
</li><li>Rod is Rod Taylor <<a href="mailto:pg@rbt.ca">pg@rbt.ca</a>>
</li><li>Simon is Simon Riggs <<a href="mailto:simon@2ndquadrant.com">simon@2ndquadrant.com</a>>
</li><li>Stephan is Stephan Szabo <<a href="mailto:sszabo@megazone23.bigpanda.com">sszabo@megazone23.bigpanda.com</a>>
</li><li>Tatsuo is Tatsuo Ishii <<a href="mailto:t-ishii@sra.co.jp">t-ishii@sra.co.jp</a>> of Software Research Assoc.
</li><li>Tom is Tom Lane <<a href="mailto:tgl@sss.pgh.pa.us">tgl@sss.pgh.pa.us</a>> of Red Hat
</li></ul>
</li></ul></li></ul>
</body>
</html>
|
