Tom,
> Eyeing the patch queue and wondering how much of it is really going to
> get in, I'm not sure that eight point two and a half wouldn't be a more
> appropriate name. It's been a short devel cycle and one almost entirely
> focused on performance, not user-visible features.
Ah, in my enthusi
Josh Berkus <[EMAIL PROTECTED]> writes:
> ... should this be 9.0 instead of 8.3?
No. This is mere version-number-inflation.
Eyeing the patch queue and wondering how much of it is really going to
get in, I'm not sure that eight point two and a half wouldn't be a more
appropriate name. It's bee
Josh Berkus wrote:
Between major
improvements to performance, major changes to the file format, and changes to
implicit conversions breaking backwards compatibility, our new ability to
more-or-less stick to deadlines ...
... should this be 9.0 instead of 8.3?
Seems like it'd be both an ann
Hackers,
I was thinking about the upcoming release on my 32-hour epic airplane ordeal,
and realizing that it changes PostgreSQL in a lot of ways. Between major
improvements to performance, major changes to the file format, and changes to
implicit conversions breaking backwards compatibility, o
