88< body bgcolor ="#FFFFFF " text ="#000000 " link ="#FF0000 " vlink ="#A00000 " alink ="#0000FF ">
99< h1 > < a name ="section_1 "> PostgreSQL TODO List</ a > </ h1 >
1010< p > Current maintainer: Bruce Momjian (< a href ="mailto:bruce@momjian.us "> bruce@momjian.us</ a > )< br />
11- Last updated: Tue Mar 11 16:46:16 EDT 2008
11+ Last updated: Tue Mar 11 17:06:02 EDT 2008
1212</ p >
1313< p > The most recent version of this document can be viewed at< br />
1414< a href ="http://www.postgresql.org/docs/faqs.TODO.html "> http://www.postgresql.org/docs/faqs.TODO.html</ a > .
@@ -1284,7 +1284,31 @@ <h1><a name="section_19">Optimizer / Executor</a></h1>
12841284< p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php "> http://archives.postgresql.org/pgsql-hackers/2007-05/msg00450.php</ a >
12851285</ p >
12861286</ li > </ ul >
1287- < h1 > < a name ="section_20 "> Miscellaneous Performance</ a > </ h1 >
1287+ < h1 > < a name ="section_20 "> Background Writer</ a > </ h1 >
1288+
1289+ < ul >
1290+ < li > Consider having the background writer update the transaction status
1291+ hint bits before writing out the page
1292+ < p > Implementing this requires the background writer to have access to system
1293+ catalogs and the transaction status log.
1294+ </ p >
1295+ </ li > < li > Consider adding buffers the background writer finds reusable to the
1296+ free list
1297+ < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php "> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</ a >
1298+ </ p >
1299+ </ li > < li > Automatically tune bgwriter_delay based on activity rather then using a
1300+ fixed interval
1301+ < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php "> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</ a >
1302+ </ p >
1303+ </ li > < li > Consider wither increasing BM_MAX_USAGE_COUNT improves performance
1304+ < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php "> http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php</ a >
1305+ </ p >
1306+ </ li > < li > Test to see if calling PreallocXlogFiles() from the background writer
1307+ will help with WAL segment creation latency
1308+ < p > < a href ="http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php "> http://archives.postgresql.org/pgsql-patches/2007-06/msg00340.php</ a >
1309+ </ p >
1310+ </ li > </ ul >
1311+ < h1 > < a name ="section_21 "> Miscellaneous Performance</ a > </ h1 >
12881312
12891313< ul >
12901314 < li > Do async I/O for faster random read-ahead of data
@@ -1315,22 +1339,6 @@ <h1><a name="section_20">Miscellaneous Performance</a></h1>
13151339 two because a heap row cannot be more than 64k in length
13161340 </ li > </ ul >
13171341 </ li > < li > Consider increasing NUM_CLOG_BUFFERS
1318- </ li > < li > Consider having the background writer update the transaction status
1319- hint bits before writing out the page
1320- < p > Implementing this requires the background writer to have access to system
1321- catalogs and the transaction status log.
1322- </ p >
1323- </ li > < li > Consider adding buffers the background writer finds reusable to the
1324- free list
1325- < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php "> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</ a >
1326- </ p >
1327- </ li > < li > Automatically tune bgwriter_delay based on activity rather then using a
1328- fixed interval
1329- < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php "> http://archives.postgresql.org/pgsql-hackers/2007-04/msg00781.php</ a >
1330- </ p >
1331- </ li > < li > Consider wither increasing BM_MAX_USAGE_COUNT improves performance
1332- < p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php "> http://archives.postgresql.org/pgsql-hackers/2007-06/msg01007.php</ a >
1333- </ p >
13341342 </ li > < li > Allow user configuration of TOAST thresholds
13351343< p > < a href ="http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php "> http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php</ a >
13361344</ p >
@@ -1351,7 +1359,7 @@ <h1><a name="section_20">Miscellaneous Performance</a></h1>
13511359< p > < a href ="http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php "> http://archives.postgresql.org/pgsql-bugs/2008-02/msg00157.php</ a >
13521360</ p >
13531361</ li > </ ul >
1354- < h1 > < a name ="section_21 "> Source Code</ a > </ h1 >
1362+ < h1 > < a name ="section_22 "> Source Code</ a > </ h1 >
13551363
13561364< ul >
13571365 < li > Add use of 'const' for variables in source tree
@@ -1418,7 +1426,7 @@ <h1><a name="section_21">Source Code</a></h1>
14181426 of result sets using new statement protocol
14191427 </ li > </ ul >
14201428</ li > </ ul >
1421- < h1 > < a name ="section_22 "> Exotic Features</ a > </ h1 >
1429+ < h1 > < a name ="section_23 "> Exotic Features</ a > </ h1 >
14221430
14231431< ul >
14241432 < li > Add pre-parsing phase that converts non-ISO syntax to supported
@@ -1445,7 +1453,7 @@ <h1><a name="section_22">Exotic Features</a></h1>
14451453< p > < a href ="http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php "> http://archives.postgresql.org/pgsql-hackers/2008-01/msg00893.php</ a >
14461454</ p >
14471455</ li > </ ul >
1448- < h1 > < a name ="section_23 "> Features We Do < u > Not</ u > Want</ a > </ h1 >
1456+ < h1 > < a name ="section_24 "> Features We Do < u > Not</ u > Want</ a > </ h1 >
14491457
14501458< ul >
14511459 < li > All backends running as threads in a single process (not wanted)
0 commit comments