2010年12月18日

[installer 2609] postgresql-9.0.2, 8.4.6, 8.3.13, 8.2.19, 8.1.23

postgresql-9.0.2, 8.4.6, 8.3.13, 8.2.19, 8.1.23 出ています。

☆ postgresql-9.0.2
http://www.postgresql.org/
ftp://ftp.postgresql.org/pub/source/v9.0.2/postgresql-9.0.2.tar.gz

Release 9.0.2

Release date: 2010-12-16

This release contains a variety of fixes from 9.0.1. For information
about new features in the 9.0 major release, see the Section called
Release 9.0.
__________________________________________________________________

Migration to Version 9.0.2

A dump/restore is not required for those running 9.0.X.
__________________________________________________________________

Changes

* Force the default wal_sync_method to be fdatasync on Linux (Tom
Lane, Marti Raudsepp)
The default on Linux has actually been fdatasync for many years,
but recent kernel changes caused PostgreSQL to choose open_datasync
instead. This choice did not result in any performance improvement,
and caused outright failures on certain filesystems, notably ext4
with the data=journal mount option.
* Fix "too many KnownAssignedXids" error during Hot Standby replay
(Heikki Linnakangas)
* Fix race condition in lock acquisition during Hot Standby (Simon
Riggs)
* Avoid unnecessary conflicts during Hot Standby (Simon Riggs)
This fixes some cases where replay was considered to conflict with
standby queries (causing delay of replay or possibly cancellation
of the queries), but there was no real conflict.
* Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
This could result in "bad buffer id: 0" failures or corruption of
index contents during replication.
* Fix recovery from base backup when the starting checkpoint WAL
record is not in the same WAL segment as its redo point (Jeff
Davis)
* Fix corner-case bug when streaming replication is enabled
immediately after creating the master database cluster (Heikki
Linnakangas)
* Fix persistent slowdown of autovacuum workers when multiple workers
remain active for a long time (Tom Lane)
The effective vacuum_cost_limit for an autovacuum worker could drop
to nearly zero if it processed enough tables, causing it to run
extremely slowly.
* Fix long-term memory leak in autovacuum launcher (Alvaro Herrera)
* Avoid failure when trying to report an impending transaction
wraparound condition from outside a transaction (Tom Lane)
This oversight prevented recovery after transaction wraparound got
too close, because database startup processing would fail.
* Add support for detecting register-stack overrun on IA64 (Tom Lane)
The IA64 architecture has two hardware stacks. Full prevention of
stack-overrun failures requires checking both.
* Add a check for stack overflow in copyObject() (Tom Lane)
Certain code paths could crash due to stack overflow given a
sufficiently complex query.
* Fix detection of page splits in temporary GiST indexes (Heikki
Linnakangas)
It is possible to have a "concurrent" page split in a temporary
index, if for example there is an open cursor scanning the index
when an insertion is done. GiST failed to detect this case and
hence could deliver wrong results when execution of the cursor
continued.
* Fix error checking during early connection processing (Tom Lane)
The check for too many child processes was skipped in some cases,
possibly leading to postmaster crash when attempting to add the new
child process to fixed-size arrays.
* Improve efficiency of window functions (Tom Lane)
Certain cases where a large number of tuples needed to be read in
advance, but work_mem was large enough to allow them all to be held
in memory, were unexpectedly slow. percent_rank(), cume_dist() and
ntile() in particular were subject to this problem.
* Avoid memory leakage while "ANALYZE"'ing complex index expressions
(Tom Lane)
* Ensure an index that uses a whole-row Var still depends on its
table (Tom Lane)
An index declared like create index i on t (foo(t.*)) would not
automatically get dropped when its table was dropped.
* Add missing support in "DROP OWNED BY" for removing foreign data
wrapper/server privileges belonging to a user (Heikki Linnakangas)
* Do not "inline" a SQL function with multiple OUT parameters (Tom
Lane)
This avoids a possible crash due to loss of information about the
expected result rowtype.
* Fix crash when inline-ing a set-returning function whose argument
list contains a reference to an inline-able user function (Tom
Lane)
* Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
attached to the VALUES part of INSERT ... VALUES (Tom Lane)
* Make the OFF keyword unreserved (Heikki Linnakangas)
This prevents problems with using off as a variable name in
PL/pgSQL. That worked before 9.0, but was now broken because
PL/pgSQL now treats all core reserved words as reserved.
* Fix constant-folding of COALESCE() expressions (Tom Lane)
The planner would sometimes attempt to evaluate sub-expressions
that in fact could never be reached, possibly leading to unexpected
errors.
* Fix "could not find pathkey item to sort" planner failure with
comparison of whole-row Vars (Tom Lane)
* Fix postmaster crash when connection acceptance (accept() or one of
the calls made immediately after it) fails, and the postmaster was
compiled with GSSAPI support (Alexander Chernikov)
* Retry after receiving an invalid response packet from a RADIUS
authentication server (Magnus Hagander)
This fixes a low-risk potential denial of service condition.
* Fix missed unlink of temporary files when log_temp_files is active
(Tom Lane)
If an error occurred while attempting to emit the log message, the
unlink was not done, resulting in accumulation of temp files.
* Add print functionality for InhRelation nodes (Tom Lane)
This avoids a failure when debug_print_parse is enabled and certain
types of query are executed.
* Fix incorrect calculation of distance from a point to a horizontal
line segment (Tom Lane)
This bug affected several different geometric distance-measurement
operators.
* Fix incorrect calculation of transaction status in ecpg (Itagaki
Takahiro)
* Fix errors in psql's Unicode-escape support (Tom Lane)
* Speed up parallel pg_restore when the archive contains many large
objects (blobs) (Tom Lane)
* Fix PL/pgSQL's handling of "simple" expressions to not fail in
recursion or error-recovery cases (Tom Lane)
* Fix PL/pgSQL's error reporting for no-such-column cases (Tom Lane)
As of 9.0, it would sometimes report "missing FROM-clause entry for
table foo" when "record foo has no field bar" would be more
appropriate.
* Fix PL/Python to honor typmod (i.e., length or precision
restrictions) when assigning to tuple fields (Tom Lane)
This fixes a regression from 8.4.
* Fix PL/Python's handling of set-returning functions (Jan Urbanski)
Attempts to call SPI functions within the iterator generating a set
result would fail.
* Fix bug in "contrib/cube"'s GiST picksplit algorithm (Alexander
Korotkov)
This could result in considerable inefficiency, though not actually
incorrect answers, in a GiST index on a cube column. If you have
such an index, consider "REINDEX"ing it after installing this
update.
* Don't emit "identifier will be truncated" notices in
"contrib/dblink" except when creating new connections (Itagaki
Takahiro)
* Fix potential coredump on missing public key in "contrib/pgcrypto"
(Marti Raudsepp)
* Fix buffer overrun in "contrib/pg_upgrade" (Hernan Gonzalez)
* Fix memory leak in "contrib/xml2"'s XPath query functions (Tom
Lane)
* Update time zone data files to tzdata release 2010o for DST law
changes in Fiji and Samoa; also historical corrections for Hong
Kong.


☆ postgresql-8.4.6
http://www.postgresql.org/
ftp://ftp.postgresql.org/pub/source/v8.4.6/postgresql-8.4.6.tar.gz

Release 8.4.6

Release date: 2010-12-16

This release contains a variety of fixes from 8.4.5. For information
about new features in the 8.4 major release, see the Section called
Release 8.4.
__________________________________________________________________

Migration to Version 8.4.6

A dump/restore is not required for those running 8.4.X. However, if you
are upgrading from a version earlier than 8.4.2, see the release notes
for 8.4.2.
__________________________________________________________________

Changes

* Force the default wal_sync_method to be fdatasync on Linux (Tom
Lane, Marti Raudsepp)
The default on Linux has actually been fdatasync for many years,
but recent kernel changes caused PostgreSQL to choose open_datasync
instead. This choice did not result in any performance improvement,
and caused outright failures on certain filesystems, notably ext4
with the data=journal mount option.
* Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
This could result in "bad buffer id: 0" failures or corruption of
index contents during replication.
* Fix recovery from base backup when the starting checkpoint WAL
record is not in the same WAL segment as its redo point (Jeff
Davis)
* Fix persistent slowdown of autovacuum workers when multiple workers
remain active for a long time (Tom Lane)
The effective vacuum_cost_limit for an autovacuum worker could drop
to nearly zero if it processed enough tables, causing it to run
extremely slowly.
* Add support for detecting register-stack overrun on IA64 (Tom Lane)
The IA64 architecture has two hardware stacks. Full prevention of
stack-overrun failures requires checking both.
* Add a check for stack overflow in copyObject() (Tom Lane)
Certain code paths could crash due to stack overflow given a
sufficiently complex query.
* Fix detection of page splits in temporary GiST indexes (Heikki
Linnakangas)
It is possible to have a "concurrent" page split in a temporary
index, if for example there is an open cursor scanning the index
when an insertion is done. GiST failed to detect this case and
hence could deliver wrong results when execution of the cursor
continued.
* Fix error checking during early connection processing (Tom Lane)
The check for too many child processes was skipped in some cases,
possibly leading to postmaster crash when attempting to add the new
child process to fixed-size arrays.
* Improve efficiency of window functions (Tom Lane)
Certain cases where a large number of tuples needed to be read in
advance, but work_mem was large enough to allow them all to be held
in memory, were unexpectedly slow. percent_rank(), cume_dist() and
ntile() in particular were subject to this problem.
* Avoid memory leakage while "ANALYZE"'ing complex index expressions
(Tom Lane)
* Ensure an index that uses a whole-row Var still depends on its
table (Tom Lane)
An index declared like create index i on t (foo(t.*)) would not
automatically get dropped when its table was dropped.
* Do not "inline" a SQL function with multiple OUT parameters (Tom
Lane)
This avoids a possible crash due to loss of information about the
expected result rowtype.
* Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
attached to the VALUES part of INSERT ... VALUES (Tom Lane)
* Fix constant-folding of COALESCE() expressions (Tom Lane)
The planner would sometimes attempt to evaluate sub-expressions
that in fact could never be reached, possibly leading to unexpected
errors.
* Fix postmaster crash when connection acceptance (accept() or one of
the calls made immediately after it) fails, and the postmaster was
compiled with GSSAPI support (Alexander Chernikov)
* Fix missed unlink of temporary files when log_temp_files is active
(Tom Lane)
If an error occurred while attempting to emit the log message, the
unlink was not done, resulting in accumulation of temp files.
* Add print functionality for InhRelation nodes (Tom Lane)
This avoids a failure when debug_print_parse is enabled and certain
types of query are executed.
* Fix incorrect calculation of distance from a point to a horizontal
line segment (Tom Lane)
This bug affected several different geometric distance-measurement
operators.
* Fix incorrect calculation of transaction status in ecpg (Itagaki
Takahiro)
* Fix PL/pgSQL's handling of "simple" expressions to not fail in
recursion or error-recovery cases (Tom Lane)
* Fix PL/Python's handling of set-returning functions (Jan Urbanski)
Attempts to call SPI functions within the iterator generating a set
result would fail.
* Fix bug in "contrib/cube"'s GiST picksplit algorithm (Alexander
Korotkov)
This could result in considerable inefficiency, though not actually
incorrect answers, in a GiST index on a cube column. If you have
such an index, consider "REINDEX"ing it after installing this
update.
* Don't emit "identifier will be truncated" notices in
"contrib/dblink" except when creating new connections (Itagaki
Takahiro)
* Fix potential coredump on missing public key in "contrib/pgcrypto"
(Marti Raudsepp)
* Fix memory leak in "contrib/xml2"'s XPath query functions (Tom
Lane)
* Update time zone data files to tzdata release 2010o for DST law
changes in Fiji and Samoa; also historical corrections for Hong
Kong.


☆ postgresql-8.3.13
http://www.postgresql.org/
ftp://ftp.postgresql.org/pub/source/v8.3.13/postgresql-8.3.13.tar.gz

Release 8.3.13

Release date: 2010-12-16

This release contains a variety of fixes from 8.3.12. For information
about new features in the 8.3 major release, see the Section called
Release 8.3.
__________________________________________________________________

Migration to Version 8.3.13

A dump/restore is not required for those running 8.3.X. However, if you
are upgrading from a version earlier than 8.3.8, see the release notes
for 8.3.8.
__________________________________________________________________

Changes

* Force the default wal_sync_method to be fdatasync on Linux (Tom
Lane, Marti Raudsepp)
The default on Linux has actually been fdatasync for many years,
but recent kernel changes caused PostgreSQL to choose open_datasync
instead. This choice did not result in any performance improvement,
and caused outright failures on certain filesystems, notably ext4
with the data=journal mount option.
* Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
This could result in "bad buffer id: 0" failures or corruption of
index contents during replication.
* Fix recovery from base backup when the starting checkpoint WAL
record is not in the same WAL segment as its redo point (Jeff
Davis)
* Fix persistent slowdown of autovacuum workers when multiple workers
remain active for a long time (Tom Lane)
The effective vacuum_cost_limit for an autovacuum worker could drop
to nearly zero if it processed enough tables, causing it to run
extremely slowly.
* Add support for detecting register-stack overrun on IA64 (Tom Lane)
The IA64 architecture has two hardware stacks. Full prevention of
stack-overrun failures requires checking both.
* Add a check for stack overflow in copyObject() (Tom Lane)
Certain code paths could crash due to stack overflow given a
sufficiently complex query.
* Fix detection of page splits in temporary GiST indexes (Heikki
Linnakangas)
It is possible to have a "concurrent" page split in a temporary
index, if for example there is an open cursor scanning the index
when an insertion is done. GiST failed to detect this case and
hence could deliver wrong results when execution of the cursor
continued.
* Avoid memory leakage while "ANALYZE"'ing complex index expressions
(Tom Lane)
* Ensure an index that uses a whole-row Var still depends on its
table (Tom Lane)
An index declared like create index i on t (foo(t.*)) would not
automatically get dropped when its table was dropped.
* Do not "inline" a SQL function with multiple OUT parameters (Tom
Lane)
This avoids a possible crash due to loss of information about the
expected result rowtype.
* Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
attached to the VALUES part of INSERT ... VALUES (Tom Lane)
* Fix constant-folding of COALESCE() expressions (Tom Lane)
The planner would sometimes attempt to evaluate sub-expressions
that in fact could never be reached, possibly leading to unexpected
errors.
* Fix postmaster crash when connection acceptance (accept() or one of
the calls made immediately after it) fails, and the postmaster was
compiled with GSSAPI support (Alexander Chernikov)
* Fix missed unlink of temporary files when log_temp_files is active
(Tom Lane)
If an error occurred while attempting to emit the log message, the
unlink was not done, resulting in accumulation of temp files.
* Add print functionality for InhRelation nodes (Tom Lane)
This avoids a failure when debug_print_parse is enabled and certain
types of query are executed.
* Fix incorrect calculation of distance from a point to a horizontal
line segment (Tom Lane)
This bug affected several different geometric distance-measurement
operators.
* Fix PL/pgSQL's handling of "simple" expressions to not fail in
recursion or error-recovery cases (Tom Lane)
* Fix PL/Python's handling of set-returning functions (Jan Urbanski)
Attempts to call SPI functions within the iterator generating a set
result would fail.
* Fix bug in "contrib/cube"'s GiST picksplit algorithm (Alexander
Korotkov)
This could result in considerable inefficiency, though not actually
incorrect answers, in a GiST index on a cube column. If you have
such an index, consider "REINDEX"ing it after installing this
update.
* Don't emit "identifier will be truncated" notices in
"contrib/dblink" except when creating new connections (Itagaki
Takahiro)
* Fix potential coredump on missing public key in "contrib/pgcrypto"
(Marti Raudsepp)
* Fix memory leak in "contrib/xml2"'s XPath query functions (Tom
Lane)
* Update time zone data files to tzdata release 2010o for DST law
changes in Fiji and Samoa; also historical corrections for Hong
Kong.


☆ postgresql-8.2.19
http://www.postgresql.org/
ftp://ftp.postgresql.org/pub/source/v8.2.19/postgresql-8.2.19.tar.gz

Release 8.2.19

Release date: 2010-12-16

This release contains a variety of fixes from 8.2.18. For information
about new features in the 8.2 major release, see the Section called
Release 8.2.
__________________________________________________________________

Migration to Version 8.2.19

A dump/restore is not required for those running 8.2.X. However, if you
are upgrading from a version earlier than 8.2.14, see the release notes
for 8.2.14.
__________________________________________________________________

Changes

* Force the default wal_sync_method to be fdatasync on Linux (Tom
Lane, Marti Raudsepp)
The default on Linux has actually been fdatasync for many years,
but recent kernel changes caused PostgreSQL to choose open_datasync
instead. This choice did not result in any performance improvement,
and caused outright failures on certain filesystems, notably ext4
with the data=journal mount option.
* Fix assorted bugs in WAL replay logic for GIN indexes (Tom Lane)
This could result in "bad buffer id: 0" failures or corruption of
index contents during replication.
* Fix recovery from base backup when the starting checkpoint WAL
record is not in the same WAL segment as its redo point (Jeff
Davis)
* Add support for detecting register-stack overrun on IA64 (Tom Lane)
The IA64 architecture has two hardware stacks. Full prevention of
stack-overrun failures requires checking both.
* Add a check for stack overflow in copyObject() (Tom Lane)
Certain code paths could crash due to stack overflow given a
sufficiently complex query.
* Fix detection of page splits in temporary GiST indexes (Heikki
Linnakangas)
It is possible to have a "concurrent" page split in a temporary
index, if for example there is an open cursor scanning the index
when an insertion is done. GiST failed to detect this case and
hence could deliver wrong results when execution of the cursor
continued.
* Avoid memory leakage while "ANALYZE"'ing complex index expressions
(Tom Lane)
* Ensure an index that uses a whole-row Var still depends on its
table (Tom Lane)
An index declared like create index i on t (foo(t.*)) would not
automatically get dropped when its table was dropped.
* Do not "inline" a SQL function with multiple OUT parameters (Tom
Lane)
This avoids a possible crash due to loss of information about the
expected result rowtype.
* Behave correctly if ORDER BY, LIMIT, FOR UPDATE, or WITH is
attached to the VALUES part of INSERT ... VALUES (Tom Lane)
* Fix constant-folding of COALESCE() expressions (Tom Lane)
The planner would sometimes attempt to evaluate sub-expressions
that in fact could never be reached, possibly leading to unexpected
errors.
* Add print functionality for InhRelation nodes (Tom Lane)
This avoids a failure when debug_print_parse is enabled and certain
types of query are executed.
* Fix incorrect calculation of distance from a point to a horizontal
line segment (Tom Lane)
This bug affected several different geometric distance-measurement
operators.
* Fix PL/pgSQL's handling of "simple" expressions to not fail in
recursion or error-recovery cases (Tom Lane)
* Fix PL/Python's handling of set-returning functions (Jan Urbanski)
Attempts to call SPI functions within the iterator generating a set
result would fail.
* Fix bug in "contrib/cube"'s GiST picksplit algorithm (Alexander
Korotkov)
This could result in considerable inefficiency, though not actually
incorrect answers, in a GiST index on a cube column. If you have
such an index, consider "REINDEX"ing it after installing this
update.
* Don't emit "identifier will be truncated" notices in
"contrib/dblink" except when creating new connections (Itagaki
Takahiro)
* Fix potential coredump on missing public key in "contrib/pgcrypto"
(Marti Raudsepp)
* Fix memory leak in "contrib/xml2"'s XPath query functions (Tom
Lane)
* Update time zone data files to tzdata release 2010o for DST law
changes in Fiji and Samoa; also historical corrections for Hong
Kong.


☆ postgresql-8.1.23
http://www.postgresql.org/
ftp://ftp.postgresql.org/pub/source/v8.1.23/postgresql-8.1.23.tar.gz

Release 8.1.23

Release date: 2010-12-16

This release contains a variety of fixes from 8.1.22. For information
about new features in the 8.1 major release, see the Section called
Release 8.1.

This is expected to be the last PostgreSQL release in the 8.1.X series.
Users are encouraged to update to a newer release branch soon.
__________________________________________________________________

Migration to Version 8.1.23

A dump/restore is not required for those running 8.1.X. However, if you
are upgrading from a version earlier than 8.1.18, see the release notes
for 8.1.18.
__________________________________________________________________

Changes

* Force the default wal_sync_method to be fdatasync on Linux (Tom
Lane, Marti Raudsepp)
The default on Linux has actually been fdatasync for many years,
but recent kernel changes caused PostgreSQL to choose open_datasync
instead. This choice did not result in any performance improvement,
and caused outright failures on certain filesystems, notably ext4
with the data=journal mount option.
* Fix recovery from base backup when the starting checkpoint WAL
record is not in the same WAL segment as its redo point (Jeff
Davis)
* Add support for detecting register-stack overrun on IA64 (Tom Lane)
The IA64 architecture has two hardware stacks. Full prevention of
stack-overrun failures requires checking both.
* Add a check for stack overflow in copyObject() (Tom Lane)
Certain code paths could crash due to stack overflow given a
sufficiently complex query.
* Fix detection of page splits in temporary GiST indexes (Heikki
Linnakangas)
It is possible to have a "concurrent" page split in a temporary
index, if for example there is an open cursor scanning the index
when an insertion is done. GiST failed to detect this case and
hence could deliver wrong results when execution of the cursor
continued.
* Avoid memory leakage while "ANALYZE"'ing complex index expressions
(Tom Lane)
* Ensure an index that uses a whole-row Var still depends on its
table (Tom Lane)
An index declared like create index i on t (foo(t.*)) would not
automatically get dropped when its table was dropped.
* Do not "inline" a SQL function with multiple OUT parameters (Tom
Lane)
This avoids a possible crash due to loss of information about the
expected result rowtype.
* Fix constant-folding of COALESCE() expressions (Tom Lane)
The planner would sometimes attempt to evaluate sub-expressions
that in fact could never be reached, possibly leading to unexpected
errors.
* Add print functionality for InhRelation nodes (Tom Lane)
This avoids a failure when debug_print_parse is enabled and certain
types of query are executed.
* Fix incorrect calculation of distance from a point to a horizontal
line segment (Tom Lane)
This bug affected several different geometric distance-measurement
operators.
* Fix PL/pgSQL's handling of "simple" expressions to not fail in
recursion or error-recovery cases (Tom Lane)
* Fix bug in "contrib/cube"'s GiST picksplit algorithm (Alexander
Korotkov)
This could result in considerable inefficiency, though not actually
incorrect answers, in a GiST index on a cube column. If you have
such an index, consider "REINDEX"ing it after installing this
update.
* Don't emit "identifier will be truncated" notices in
"contrib/dblink" except when creating new connections (Itagaki
Takahiro)
* Fix potential coredump on missing public key in "contrib/pgcrypto"
(Marti Raudsepp)
* Fix memory leak in "contrib/xml2"'s XPath query functions (Tom
Lane)
* Update time zone data files to tzdata release 2010o for DST law
changes in Fiji and Samoa; also historical corrections for Hong
Kong.

----
こがよういちろう


投稿者 xml-rpc : 2010年12月18日 12:35
役に立ちました?:
過去のフィードバック 平均:(0) 総合:(0) 投票回数:(0)
本記事へのTrackback: http://hoop.euqset.org/blog/mt-tb2006.cgi/100796
トラックバック
コメント
コメントする




画像の中に見える文字を入力してください。