quadkmfk.blogg.se

This is because new databases are created by copying directories. Prevent query cancel packets from being replayed by an attacker, especially when using SSLĬonsider supporting incremental base backupsĪllow 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Ĭurrently all objects in the default database tablespace must have default tablespace specifications. Another idea is to allow separate configuration files for each module, or allow arbitrary SET commands to be passed to them. This would allow administrators to see more detailed information from specific sections of the backend, e.g. The flow should be:ĭesirability -> Design -> Implement -> Test -> Review -> CommitĪdministration Check for unreferenced table files created by transactions that were in-progress when the server terminated abruptlyĪllow log_min_messages to be specified on a per-module basis Always discuss design on Hackers list before starting to code. Do not assume that you can select one, code it and then expect it to be committed. When selecting items listed below, be prepared to first discuss the value of the feature. Some of these items might have become unnecessary since they were added - others might be desirable but the implementation might be unclear. WARNING for Developers: Unfortunately this list does not contain all the information necessary for someone to start coding a feature. Please do not add or remove items here without discussion on the mailing list. Such items should be retired to the Not Worth Doing page.įor help on editing this list, please see Talk:Todo. Over time, it may become clear that a TODO item has become outdated or otherwise determined to be either too controversial or not worth the development effort. - marks changes that are done, and will appear in the PostgreSQL 15 release.

There is also a development information page. If you would like to work on an item, please read the Developer FAQ first. Many of these items are hard, and some are perhaps impossible. This list contains some known PostgreSQL bugs, some feature requests, and some things we are not even sure we want.