Thread: Upcoming Beta

As you probably know, PostgreSQL is quickly approaching the beta period
for its next release (7.3).

It would be heavily appreciated if you could attack the new source base
starting now and throughout the beta period in an attempt to make the
next release extra secure and stable from the outset.

More to the point, I'd love material I could show the local VPs as to a
reason they should upgrade to 7.3 from either other products or previous
versions of PostgreSQL.   The necessary material could be as simple as
the test cases run against the new version and it's status (pass, fail
with immediate fix, fail with major rework required (7.4 fix?)).  I've
seen four cases which failed, but how many succeeded and what kind of
test were they?

If possible (based on group decision) it would be great if this material
could be included or linked to from the release notes.

Keep up the excellent work.

Thanks,Rod

Hi.
There is no need to ask me to attack a postgresql source code,
as long as i remember myself, i was always in studing someone's source code
or disasm output..
By the way, the code i write being a plain web programmer, even for small
projects is fairly buggy:-))).
One little thing saves me a bit - i am using a perl, and the code itself
dont suffer from the buffer/integer overflows much,
not talking about DBD::Pg.

So i can repeat the above, don't ask me to do the things which i am doing
24 hours in a day...

Best regards.


________________________________________________________________________
This letter has been delivered unencrypted. We'd like to remind you that
the full protection of e-mail correspondence is provided by S-mail
encryption mechanisms if only both, Sender and Recipient use S-mail.
Register at S-mail.com: http://www.s-mail.com/inf/en