From: | "Shane Wright" <shane(dot)wright(at)edigitalresearch(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Upgrade to 8.3.0? |
Date: | 2008-02-29 18:37:01 |
Message-ID: | 952015000A644E44B2FB8759E151093B6FFAC0@exchange11.ad.edigitalresearch.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hi,
I'm considering an upgrade to 8.3.0 for some internal databases - would
normally wait until at least .1 release of anything for safety but
there's a lot of nice sounding stuff here!
After trawling the bug logs and doing some testing on some servers here
all looks ok except for this bug around VACUUM FULL and HOT tables:
http://archives.postgresql.org/pgsql-bugs/2008-02/msg00068.php
So my questions are thus...
- Is the HOT/VACUUMFULL bug above dangerous or is its biggest
side-effect an error until a non-full vacuum is run?
- Has anyone spotted anyone else that would discourage an
upgrade at this stage?
If it helps, our use of SQL is fairly basic - nothing fancy, and nothing
Postgres-specific.
Any help appreciated,
Thanks
Shane
From | Date | Subject | |
---|---|---|---|
Next Message | abracadabuda | 2008-02-29 18:40:18 | Re: pgsql structure export to XML |
Previous Message | Dan Armbrust | 2008-02-29 18:34:28 | Re: errors in pg_restore on windows? |