Re: Guessing future postgresql features

Поиск
Список
Период
Сортировка
От Gregory Stark
Тема Re: Guessing future postgresql features
Дата
Msg-id 87ve3278h7.fsf@oxford.xeocode.com
обсуждение исходный текст
Ответ на Guessing future postgresql features  (Rafael Martinez <r.m.guerrero@usit.uio.no>)
Список pgsql-hackers
"Rafael Martinez" <r.m.guerrero@usit.uio.no> writes:

> * Update-in-place optimizations which enhance OLTP performance
> * Improve XML support

These made it into 8.3. There could be more enhancements and more XML support
but you're probably looking at the stuff which already made 8.3.

> * Elimination of vacuum

Nobody's really proposed eliminating vacuum altogether but we're slowly
chipping away at it. One of the projects on the table for 8.4 would make it
much more efficient, especially for large tables which are partly static. So i
would say "faster vacuum with reduced impact" rather than "elimination"

> * Auto-tuning / auto-configuration
> * Easy update-in-place - 'pgmigrator'
> * Auto partitioning / Dynamic partitioning
> * External tables interfaces (SQL/MED compliant)
> * More exotic datatypes

All of these are on the table to one degree or another. But there's no
guarantees.

> * More SQL99 and SQL2003 features
> * More query optimizer improvements

These are pretty safe bets. I think Tom's already done some optimizer
improvements :)

> * Pre-parsing phase that converts non-ISO syntax to supported syntax.

I don't know what this refers to but it doesn't sound like the kind of thing
Postgres gets involved in.

--  Gregory Stark EnterpriseDB          http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services!


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Tom Lane
Дата:
Сообщение: How embarrassing: optimization of a one-shot query doesn't work
Следующее
От: Stephen Frost
Дата:
Сообщение: Re: How embarrassing: optimization of a one-shot query doesn't work