Re: [HACKERS] RI status report #2 - Mailing list pgsql-hackers

From Lamar Owen
Subject Re: [HACKERS] RI status report #2
Date
Msg-id 37F263B6.90EFAF29@wgcr.org
Whole thread Raw
In response to Re: [HACKERS] RI status report #2  (Bruce Momjian <maillist@candle.pha.pa.us>)
Responses Re: [HACKERS] RI status report #2
List pgsql-hackers
Bruce Momjian wrote:
> Yikes.  I was just talking to Thomas Lockhart by phone, and was saying
> that I thought 6.6 would be a small, incremental release after the
> changes in 6.5.*.  Obviously, 6.6 is going to be as full-featured as
> earlier releases.

And that surprises you??  Even in the short two years I've used
PostgreSQL, I have grown accustomed to major changes every major
version.  First there was the NOT NULL (and scads of other) features to
compel me to go from 6.1.1 to 6.2, then there were subselects (and
vastly improved documentation) to get me up to 6.3, then there were
views, rules, and the new protocol to make 6.4 a must-cc event, then
MVCC....  And now I'm maintaining RPM's so I can stay on the released
bleeding edge without breaking my server policies. Whoda thunk it?

Of course, my measly list above doesn't do the development justice -- as
one look at the changelog will show.

Lamar Owen
WGCR Internet Radio


pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] RI status report #2
Next
From: Lamar Owen
Date:
Subject: Non-beta RPMS for RedHat Linux -- PostgreSQL 6.5.2