On Fri, Jul 1, 2011 at 6:06 PM, Josh Berkus <josh@agliodbs.com> wrote:
>> That sounds reasonable to me. I'll be on vacation then, but (1) I'm
>> not really involved in pushing the release out the door and (2) I
>> should have Internet access if push comes to shove.
>
> We seem to still have some blockers ...
I'm only seeing these two:
* ALTER TABLE lock strength reduction patch is unsafe
* btree_gist breaks some behaviors involving <> operators
Simon fixed the first over the weekend (though I think there are a few
loose ends, see separate email on that topic) and Tom proposed a fix
for the second (which I am guessing he will implement).
Any other reason we can't or shouldn't wrap on the 11th?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
