Time to package 8.2.4
Hello,
We have had several customers get bit by the 8.2.3 stats collector bug.
It is also starting to get reported in areas such as IRC. The really bad
thing about this bug is that you won't know what is wrong unless you
know where to look, PostgreSQL will just appear slow and tying up resources.
Can we please package 8.2.4 and get it out the door?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
On Mar 24, 2007, at 1:55 AM, Joshua D. Drake wrote:
Hello,
We have had several customers get bit by the 8.2.3 stats collector
bug.
It is also starting to get reported in areas such as IRC. The
really bad
thing about this bug is that you won't know what is wrong unless you
know where to look, PostgreSQL will just appear slow and tying up
resources.Can we please package 8.2.4 and get it out the door?
+1
this is a show-stopper for me, I won't move production to 8.2, unless
that's fixed. Can't allow this to happen in production.
--
Grzegorz Jaskiewicz
C/C++ freelance for hire
Am Sat, 24 Mar 2007 13:19:28 +0100 hat Grzegorz Jaskiewicz
<gj@pointblue.com.pl> geschrieben:
On Mar 24, 2007, at 1:55 AM, Joshua D. Drake wrote:
Hello,
We have had several customers get bit by the 8.2.3 stats collector bug.
It is also starting to get reported in areas such as IRC. The really bad
thing about this bug is that you won't know what is wrong unless you
know where to look, PostgreSQL will just appear slow and tying up
resources.Can we please package 8.2.4 and get it out the door?
+1
this is a show-stopper for me, I won't move production to 8.2, unless
that's fixed. Can't allow this to happen in production.
+1
--
Hakan
We have had several customers get bit by the 8.2.3 stats collector bug.
It is also starting to get reported in areas such as IRC. The really bad
thing about this bug is that you won't know what is wrong unless you
know where to look, PostgreSQL will just appear slow and tying up
resources.
I reiterate the question. Can we please package 8.2.4.
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
Am Montag, 26. Mï¿œrz 2007 18:07 schrieb Joshua D. Drake:
I reiterate the question. Can we please package 8.2.4.
Sure, go ahead.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Peter Eisentraut wrote:
Am Montag, 26. Mï¿œrz 2007 18:07 schrieb Joshua D. Drake:
I reiterate the question. Can we please package 8.2.4.
Sure, go ahead.
Funny :). What can I do to help get 8.2.4 branched?
Joshua D. Drake
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.
We're just starting to get the process nice and streamlined with all the
various binary builds, announcements and CVE embargos (when needed).
Perhaps it's not such a good idea to start reassigning tasks to random
people (no offence JD) without discussion and agreement from those
normally responsible?
Regards, Dave.
Dave Page wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.We're just starting to get the process nice and streamlined with all the
various binary builds, announcements and CVE embargos (when needed).
Perhaps it's not such a good idea to start reassigning tasks to random
people (no offence JD) without discussion and agreement from those
normally responsible?
No offense taken, I think Peter was saying... Hey this is something you
(being me) could probably do, to help the continuation of that process.
It is (i would guess) certainly something that people don't like doing
in general and thus would help get the ball rolling.
I don't mind either way, but 8.2.4 needs to be released. If my putting
together a changes list will help with that. I will do so.
Sincerely,
Joshua D. Drake
Regards, Dave.
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
Joshua D. Drake wrote:
Dave Page wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.We're just starting to get the process nice and streamlined with all the
various binary builds, announcements and CVE embargos (when needed).
Perhaps it's not such a good idea to start reassigning tasks to random
people (no offence JD) without discussion and agreement from those
normally responsible?No offense taken, I think Peter was saying... Hey this is something you
(being me) could probably do, to help the continuation of that process.
It is (i would guess) certainly something that people don't like doing
in general and thus would help get the ball rolling.I don't mind either way, but 8.2.4 needs to be released. If my putting
together a changes list will help with that. I will do so.
I would assume that would be a big help, especially given that Bruce is
busy with the patch queue right now.
There is another point to putting it out fairly soon - we're entering
feature freeze, and most devs would likely want to focus on 8.3 at that
time. Probably a good thing to get 8.2.4 out before that (which really
means we should've started a couple of weeks back, but hey, we can't
have everything)
//Magnus
Joshua D. Drake wrote:
Dave Page wrote:
Peter Eisentraut wrote:
Joshua D. Drake wrote:
Funny :). What can I do to help get 8.2.4 branched?
There is no branching involved, but you can look into
src/tools/RELEASE_CHANGES and see what things you want to help with.
Getting a release changes list would be a start.We're just starting to get the process nice and streamlined with all the
various binary builds, announcements and CVE embargos (when needed).
Perhaps it's not such a good idea to start reassigning tasks to random
people (no offence JD) without discussion and agreement from those
normally responsible?No offense taken, I think Peter was saying... Hey this is something you
(being me) could probably do, to help the continuation of that process.
It is (i would guess) certainly something that people don't like doing
in general and thus would help get the ball rolling.I don't mind either way, but 8.2.4 needs to be released. If my putting
Yeah, I know - we should just get agreement on such procedural changes
first imho.
/D
Hello,
Below is the change log as I see it. I gleaned it from here:
http://projects.commandprompt.com/public/pgsql/log/branches/REL8_2_STABLE
If I missed anything let me know.
Sincerely,
Joshua D. Drake
* Fixed preload_shared_libraries on Windows (Bruce)
* Rearrange use of plpgsql_add_initdatums() so that only the parsing of
a DECLARE section needs to know about it. Fixes bug that caused a
DECLARE within an exception handler tried to reinitialize SQLERRM. (Tom)
* Fixed an ancient local varaiable (re)initializing error in plpgsql's
exec_stmt_block. (Tom)
* Fixed bug when localized to_char() day or month names were incorrectly
transformed to lower or upper string. (Bruce)
* Fix for early log messages getting lost on postmaster startup when
running as a service on Win32. (Magnus)
* Fixed backend crash with incorrect ts_query (tsearch2) parsing. (Teodor)
* Fixed bug in JOIN logic for planning OUTER JOINS. (Tom)
* Disallow commiting prepared transactions from a different database in
which the transaction was initiated (Heikki)
* Improve handling of psuedoconstants (Tom)
* Resolved bug with clauseless JOINS and subqueries. (Tom)
* Fixed problem in 8.2 changes that allowed "one-time" qual conditions
to be checked at plan levels below the top. (Tom)
* Adjust is_pushed_down to work correctly with INNER JOINS. (Tom)
* Fixed old bug in portal management for FETCH queries. (Tom)
* Allow Win32 pg_dump to create files larger than 2GB (Magnus)
* Made markQueryForLocking() work with nested views. (Tom)
* Fix miscalculation of stats collector's write delay. (Tom)
* Fix inline_function() to work with binary compatible cases. (Tom)
* Allow cube data type to be correctly toastable. (Teodor)
* Fix vac_update_relstats to ensure it always sends a relcache inval
message. (Tom)
* Remove unsafe calling of WSAStartup and WSACleanup on Win32. (Magnus)
* Fix race condition in pg_database_size and pg_tablespace_size. (Alvaro)
* Allow POSIX-style timezones that don't exactly many any timezone
database entry to be treated as having correct USA DST rules. (Tom)
* Fix longstanding bug with VACUUM FULL handling of update chains. (Tom)
* Fixed uninitialized value in pgstatindex that caused invalid values to
be reported in some cases (Tatsuhito Kasahara)
* Insure that read-only queries are truly read-only with
SPI_cursor_open. (Tom)
* Fixed 8.2 breakage of domains over array types. (Tom)
* Fixed parser bug (tsearch2) with UTF8 and C locales on Win32. (Teodor)
* Fix pg_wchar_table's maxmblen field of EUC_CN, EUC_TW, MULE_INTERNAL
and GB18030. (ITAGAKI Takahiro).
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate
PostgreSQL Replication: http://www.commandprompt.com/products/
