8.2 Beta 3 Now Available for Download / Testing ...

Marc G. Fournier wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As a result of there being two *known* outstanding bugs, we have just bundled
up a Beta3, to allow for testing of the recent patch concerning WAL replay ...

Please download the latest beta from:

ftp.postgresql.org:/pub/source/v8.2beta

While the mirrors themselves catch up over the next 24 hours ...

What are the bugs?

cheers

andrew

Andrew Dunstan wrote:

Marc G. Fournier wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As a result of there being two *known* outstanding bugs, we have just
bundled up a Beta3, to allow for testing of the recent patch
concerning WAL replay ...

What are the bugs?

AFAIK:

1. Tuple freezing and hint bits were not WAL-logged, which could lead to
data corruption if database crashed after VACUUM. See recent thread
titled "WAL logging freezing".

2. B-tree page deletion bug, which could lead to VACUUM erroring with
"failed to re-find parent key" message. See thread "Nasty btree deletion
bug": http://archives.postgresql.org/pgsql-hackers/2006-10/msg01373.php

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

On Tuesday 07 November 2006 13:25, Marc G. Fournier wrote:

As a result of there being two *known* outstanding bugs, we have just
bundled up a Beta3, to allow for testing of the recent patch concerning WAL
replay ...

Please download the latest beta from:

ftp.postgresql.org:/pub/source/v8.2beta

While the mirrors themselves catch up over the next 24 hours ...

Hey Marc, this url breaks consistency with previous beta builds and with the
windows beta binaries which all use an incrementing beta version number (ie.
beta3 vs. beta). I've adjusted the links on the website to match what's
actually up there, but it might be a good idea to remove the beta2 directory
from http://www.postgresql.org/ftp/source/ lest someone gets confused about
where to look for the most recent beta.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Done ...

- --On Wednesday, November 08, 2006 21:31:38 -0500 Robert Treat
<xzilla@users.sourceforge.net> wrote:

On Tuesday 07 November 2006 13:25, Marc G. Fournier wrote:

As a result of there being two *known* outstanding bugs, we have just
bundled up a Beta3, to allow for testing of the recent patch concerning WAL
replay ...

Please download the latest beta from:

ftp.postgresql.org:/pub/source/v8.2beta

While the mirrors themselves catch up over the next 24 hours ...

Hey Marc, this url breaks consistency with previous beta builds and with the
windows beta binaries which all use an incrementing beta version number (ie.
beta3 vs. beta). I've adjusted the links on the website to match what's
actually up there, but it might be a good idea to remove the beta2 directory
from http://www.postgresql.org/ftp/source/ lest someone gets confused about
where to look for the most recent beta.

--
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL

- ----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy@hub.org MSN . scrappy@hub.org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (FreeBSD)

iD8DBQFFUqVR4QvfyHIvDvMRAjyKAKCZ+TDox/aHs5iEcvC8UaVybYM5rACfcuRl
080Zda4k36bXOV8nrPxdxRA=
=CzW5
-----END PGP SIGNATURE-----

Heikki Linnakangas wrote:

Andrew Dunstan wrote:

Marc G. Fournier wrote:

As a result of there being two *known* outstanding bugs, we have
just bundled up a Beta3, to allow for testing of the recent patch
concerning WAL replay ...

What are the bugs?

AFAIK:

1. Tuple freezing and hint bits were not WAL-logged, which could lead
to data corruption if database crashed after VACUUM. See recent thread
titled "WAL logging freezing".

2. B-tree page deletion bug, which could lead to VACUUM erroring with
"failed to re-find parent key" message. See thread "Nasty btree
deletion bug":
http://archives.postgresql.org/pgsql-hackers/2006-10/msg01373.php

I assume that we also want to fix the plperl/plperlu interaction issue,
especially as it will result in changed behaviour on some platforms, at
least.

I have asked a couple of people to look over and test the patch I posted
on Sunday, but i have not had any reaction so far and feel slightly
nervous about applying it. I will make some time to do more testing
myself this weekend.

cheers

andrew