From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Getting a move on for 8.2 beta |
Date: | 2006-09-01 19:07:38 |
Message-ID: | 200609011207.38628.josh@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-www |
Tom,
> September is upon us and it doesn't seem like we are ready to ship
> a beta. I think it's time to start making some hard choices.
>
> In the main code I see these outstanding features/patches:
>
> * bitmap indexes
> * updatable views
> * GUC variable reload + refactoring (previously applied and reverted)
> * plpython improvements (needs review by someone who knows plpython)
> * plpgsql improvements for returning record types
> * patch to build on VC
What's VC?
> * make libpq default client_encoding setting from locale?
>
> In contrib we've got:
>
> * new ISBN/etc module
> * hstore (finally proposed for inclusion)
> * new sslinfo module
> * pgstattuple changes
> * removing the deadwood
This is just a delete. I've fixed the pgFoundry permissions issues and
will be loading the last CVS snapshot today. At that point, Bruce can
delete stuff.
Can you be a little clearer on which things are non-working patches, and
which things are pending due to lack of review? I'm all for bouncing
stuff that's not ready to go, but bouncing stuff because we haven't
recruited enough code reviewers is just bad practice.
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-01 19:20:24 | Re: Getting a move on for 8.2 beta |
Previous Message | Alvaro Herrera | 2006-09-01 18:52:05 | Re: Getting a move on for 8.2 beta |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-09-01 19:20:24 | Re: Getting a move on for 8.2 beta |
Previous Message | Alvaro Herrera | 2006-09-01 18:52:05 | Re: Getting a move on for 8.2 beta |