On Mon, Mar 31, 2008 at 7:02 PM, Rafael Martinez
> * Auto-tuning / auto-configuration
Perhaps. Though, people have been saying they were going to do it
since 2001, and yet nothing substantial exists.
> * Easy update-in-place - 'pgmigrator'
This should be upgrade-in-place, not update-in-place
> * More SQL99 and SQL2003 features
> * Update-in-place optimizations which enhance OLTP performance
Postgres does not have update-in-place. I would just say OLTP
> * Auto partitioning / Dynamic partitioning
> * External tables interfaces (SQL/MED compliant)
It would be nice to see distributed/federated code integrated into the
core, but I don't see it happening anytime soon.
> * More exotic datatypes
> * More query optimizer improvements
> * Elimination of vacuum
> * Improve XML support
> * Pre-parsing phase that converts non-ISO syntax to supported syntax.
Doubtful. That's a pgfoundry-type external project.
Jonah H. Harris, Sr. Software Architect | phone: 732.331.1324
EnterpriseDB Corporation | fax: 732.331.1301
499 Thornall Street, 2nd Floor | jonah(dot)harris(at)enterprisedb(dot)com
Edison, NJ 08837 | http://www.enterprisedb.com/
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2008-04-01 01:51:08|
|Subject: Re: How embarrassing: optimization of a one-shot query doesn't work |
|Previous:||From: Stephen Frost||Date: 2008-04-01 00:46:44|
|Subject: Re: How embarrassing: optimization of a one-shot querydoesn't work|