PostgreSQL 9.2 Open Items
From PostgreSQL wiki
Contents |
Project Planning
See the PostgreSQL 9.2 Development Plan.
Meta-Issues
- Review "Long Term" list of items from PostgreSQL 9.0 Open Items and PostgreSQL 9.1 Open Items
Open Issues
bgwriter/checkpointer split
- Bgwriter needs to close file handles [Simon]
- Checkpointer latch loop [Simon]
- I've hacked that area of the code until it looks OK to me, is there something else you had in mind? -- tgl
- Checkpointer doesn't send stats promptly
- Double check bgwriter/checkpointer comments
- I made a pass over these, does anyone want to do more? -- tgl
- Check new processes listed correctly in postmaster comments
- I made a pass over these, does anyone want to do more? -- tgl
index-only scans
- Make XLOG_HEAP2_VISIBLE records generate recovery snapshot conflicts so that IndexOnlyScans work on Hot Standby
- analysis
- committed patch - still would be nice to throw a soft conflict instead of a hard one
indexing
- Correct docs for SP-GIST so that example implementations shown/referred to/examples given - unusably opaque at present
- Huh? There is a pointer to the example opclasses, and in general the SPGiST docs seem to me to be at least as good as those for GiST or GIN - tgl
- Put a bound on memory usage when building large GiST indexes. (see last paragraph of this mail)
- GiST indexes vs fuzzy comparisons used by geometric types
- Alexander proposed a patch that would support the current behavior, but should we change the behavior instead?
- SP-GiST is unsafe for use by hot standby slaves
- B-tree page deletion boundary cases
pg_basebackup/pg_receivexlog
- pg_basebackup -x stream from the standby gets stuck if there is no traffic in the database
- incorrect handling of the timeout in pg_receivexlog
- pg_receivexlog requires manually restarting whenever the sending server restarts
- A brief discussion offline came up with the suggested options --auto-reconnect --auto-disconnect
other
- simple_prompt uses wrong charset (Windows)
- WAL files which were restored from the archive are archived again.
- Should we fix tuple limit handling, or redefine 9.x behavior as correct?
- The consensus seems to be to change the documentation to match the current behavior.
- Start warning on CREATE {GLOBAL | LOCAL} TEMPORARY TABLE?
- libpq URL syntax needs work for unix-socket addresses
Resolved Issues
- streaming backup should not be considered as sync standby.
- Documentation needs updating wrt visibility map/index-only scans
- change GiST implementation for range types?
- pglesslog still referenced in docs, but no 9.1 support
- Should we change the behavior of extract(epoch from timestamp)?
- search_path behavioral change
- Replace bytea_agg with string_agg(bytea,bytea)?
- pg_size_pretty(numeric)
- Reconsider the names of valid values of synchronous_commit
- nodes/*funcs.c inconsistencies
- Parameterized-path costing still needs some work
- Change syntax for non-inherited CHECK constraints?
- Aggressive memory consumption in {ts,array}_typanalyze
- Auto-ANALYZE can prevent all-visible flags from getting set, leading to failure to use index-only scans
- I've hacked the regression test case to prevent the intermittent failure. Fixing auto-ANALYZE so that the problem doesn't arise would be nice, but it seems like a research project; added that to TODO.
- patch: plpython triggers are broken for composite-type columns
- Inconsistent units in pg_stat_statements
- psql omits row count under "\x auto"
- Update the sample ps output in "monitoring-ps" section of the manual to include the new checkpointer process
- Release-note PL case folding incompatibility
- checkpointer gets confused after crash-and-restart
- On closer inspection, this was pilot error, namely misuse of the postmaster -T feature.
