Re: Major features for 9.1
От | Robert Bernier |
---|---|
Тема | Re: Major features for 9.1 |
Дата | |
Msg-id | 201104021039.51553.robert@pg-live.info обсуждение исходный текст |
Ответ на | Major features for 9.1 (Josh Berkus <josh@agliodbs.com>) |
Ответы |
Re: Major features for 9.1
|
Список | pgsql-advocacy |
Here's my thoughts... > Here's a list of the features which seem to me to be major enough to be > headliners for 9.1. Please mark which ones you think are major/not > major/not major and anything you think I've forgotten. > > ... picking 5-6 items ... > Synchronous Replication +1 it's the flavour of the day > * wCTE: Writeable Common Table Expressions +1 I'm finding myself using a lot of Common Table Expressions it's more intuitive than the more traditional BEGIN .. COMMIT paradigm especially for programmers/developers > * Per-column collations -1 > > * SSI: Serializable Snapshot Isolation > True serializability without locking. -1 You have to explain this otherwise there's no point in promoting this > * Unlogged Tables > Reason: allows using Postgres for not-valuable, high-performance data > like session tables instead of using a caching database +1 This is a sleeper. Drop the apology that it's for 'not-valuable' data. I can see a lot of places that can allow pg to enter the big-data / cassandra / hbase world > * SQL/MED with FILE_FDW +1 > * KNN-GiST: K-Nearest Neighbor Indexing > Permits indexed searches of "what's near X", greatly improving the > responsiveness of PostGIS applications and allowing new application > types to be built. -1 > * Single-command cloning, new admin tools for replication > Not sure about this one, should probably be buried in text somewhere. -1 Should be massaged as part of the continuing evolution of replication support, the first point. > * PL/Python Overhaul -1 need more details to vote on it > SEPostgres -1 requires a user-case i.e. show how a past high profile exploit could have been stopped with this mechanism in place. > Extensions +1 I suggest a user-case explanation of how would it be used
В списке pgsql-advocacy по дате отправления: