Skip site navigation (1) Skip section navigation (2)

Re: Guessing future postgresql features

From: "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com>
To: "Rafael Martinez" <r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Guessing future postgresql features
Date: 2008-04-01 01:08:14
Message-ID: 36e682920803311808se8f7597v9e57b359f3bcf127@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Mon, Mar 31, 2008 at 7:02 PM, Rafael Martinez
<r(dot)m(dot)guerrero(at)usit(dot)uio(dot)no> wrote:
>  * 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

Likely.

>  * Update-in-place optimizations which enhance OLTP performance

Postgres does not have update-in-place.  I would just say OLTP
performance enhancements.

>  * Auto partitioning / Dynamic partitioning

Likely.

>  * 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

Doubt it.

>  * More query optimizer improvements

Always

>  * Elimination of vacuum

I wish.

>  * Improve XML support

Probably.

>  * 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 LaneDate: 2008-04-01 01:51:08
Subject: Re: How embarrassing: optimization of a one-shot query doesn't work
Previous:From: Stephen FrostDate: 2008-04-01 00:46:44
Subject: Re: How embarrassing: optimization of a one-shot querydoesn't work

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group