Thread: ETA for PostgreSQL 7.3.3?
Hi guys, Feels like we've been isolating a whole bunch of bugs in 7.3.2 recently, some of which are causing crashes out in the real world. Wondering when we feel it'd be good to start assembling a 7.3.3? I'm thinking in about two weeks or so, to give a bit more time to catch bugs and stuff. Any thoughts/suggestions? Regards and best wishes, Justin Clift -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
> Feels like we've been isolating a whole bunch of bugs in 7.3.2 recently, > some of which are causing crashes out in the real world. > > Wondering when we feel it'd be good to start assembling a 7.3.3? I'm > thinking in about two weeks or so, to give a bit more time to catch bugs > and stuff. I really should fix this rowtype problem for 7.3.3 - here's hoping I find some time... Chris
Christopher Kings-Lynne wrote: >>Feels like we've been isolating a whole bunch of bugs in 7.3.2 recently, >>some of which are causing crashes out in the real world. >> >>Wondering when we feel it'd be good to start assembling a 7.3.3? I'm >>thinking in about two weeks or so, to give a bit more time to catch bugs >>and stuff. > > I really should fix this rowtype problem for 7.3.3 - here's hoping I find > some time... Agreed. I wish "time" could be purchased in bottles. Reckon we could all get together and put in wholesale orders! :) Regards and best wishes, Justin Clift > Chris -- "My grandfather once told me that there are two kinds of people: those who work and those who take the credit. He told me to try to be in the first group; there was less competition there." - Indira Gandhi
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au> writes: > I really should fix this rowtype problem for 7.3.3 - here's hoping I find > some time... I think it'll be too large and risky a change to put into 7.3.* in any case. Maybe you'll find some brilliant, obviously-correct solution --- but I'm betting that it will require messiness in a number of places. regards, tom lane