On Tue, Jan 18, 2011 at 12:16 PM, Simone Aiken <saiken@ulfheim.net> wrote:
> When I'm learning a new system I like to first learn how to use it,
> second learn its data model, third start seriously looking at the code.
> So that Todo is ideal for my learning method.
Sure - my point is just that we usually have as a criteria for any
performance related patch that it actually does improve performance.
So, we'd need a test case.
> If there is something else that would also involve studying all the system
> tables it would also be great. For example, I noticed we have column
> level comments on the web but not in the database itself. This seems
> silly. Why not have the comments in the database and have the web
> query the tables of template databases for the given versions?
Uh... I don't know what this means.
> I'm open to other suggestions as well.
Here are a few TODO items that look relatively easy to me (they may
not actually be easy when you dig in, of course):
Clear table counters on TRUNCATE
Allow the clearing of cluster-level statistics
Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME
Allow ALTER TABLE to change constraint deferrability and actions
Unfortunately we don't have a lot of easy TODOs. People keep doing
the ones we think up...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
