2012年6月 6日

[installer 3245] postgresql-9.1.4, 9.0.8, 8.4.12, 8.3.19

postgresql-9.1.4, 9.0.8, 8.4.12, 8.3.19 出ています。

2件のセキュリティホールの修正が含まれています (ひとつは DES の crypt()
の奴です)。
http://www.postgresql.org/about/news/1398/
参照のこと。

☆ postgresql-9.1.4

http://www.postgresql.org/
http://ftp.postgresql.org/pub/source/v9.1.4/postgresql-9.1.4.tar.gz

Release 9.1.4

Release Date: 2012-06-04

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

Migration to Version 9.1.4

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

However, if you use the citext data type, and you upgraded from a
previous major release by running pg_upgrade, you should run CREATE
EXTENSION citext FROM unpackaged to avoid collation-related failures in
citext operations. The same is necessary if you restore a dump from a
pre-9.1 database that contains an instance of the citext data type. If
you've already run the "CREATE EXTENSION" command before upgrading to
9.1.4, you will instead need to do manual catalog updates as explained
in the third changelog item below.

Also, if you are upgrading from a version earlier than 9.1.2, see the
release notes for 9.1.2.
__________________________________________________________________

Changes

* Fix incorrect password transformation in "contrib/pgcrypto"'s DES
crypt() function (Solar Designer)
If a password string contained the byte value 0x80, the remainder
of the password was ignored, causing the password to be much weaker
than it appeared. With this fix, the rest of the string is properly
included in the DES hash. Any stored password values that are
affected by this bug will thus no longer match, so the stored
values may need to be updated. (CVE-2012-2143)
* Ignore SECURITY DEFINER and SET attributes for a procedural
language's call handler (Tom Lane)
Applying such attributes to a call handler could crash the server.
(CVE-2012-2655)
* Make "contrib/citext"'s upgrade script fix collations of citext
arrays and domains over citext (Tom Lane)
Release 9.1.2 provided a fix for collations of citext columns and
indexes in databases upgraded or reloaded from pre-9.1
installations, but that fix was incomplete: it neglected to handle
arrays and domains over citext. This release extends the module's
upgrade script to handle these cases. As before, if you have
already run the upgrade script, you'll need to run the collation
update commands by hand instead. See the 9.1.2 release notes for
more information about doing this.
* Allow numeric timezone offsets in timestamp input to be up to 16
hours away from UTC (Tom Lane)
Some historical time zones have offsets larger than 15 hours, the
previous limit. This could result in dumped data values being
rejected during reload.
* Fix timestamp conversion to cope when the given time is exactly the
last DST transition time for the current timezone (Tom Lane)
This oversight has been there a long time, but was not noticed
previously because most DST-using zones are presumed to have an
indefinite sequence of future DST transitions.
* Fix text to name and char to name casts to perform string
truncation correctly in multibyte encodings (Karl Schnaitter)
* Fix memory copying bug in to_tsquery() (Heikki Linnakangas)
* Ensure txid_current() reports the correct epoch when executed in
hot standby (Simon Riggs)
* Fix planner's handling of outer PlaceHolderVars within subqueries
(Tom Lane)
This bug concerns sub-SELECTs that reference variables coming from
the nullable side of an outer join of the surrounding query. In
9.1, queries affected by this bug would fail with "ERROR:
Upper-level PlaceHolderVar found where not expected". But in 9.0
and 8.4, you'd silently get possibly-wrong answers, since the value
transmitted into the subquery wouldn't go to null when it should.
* Fix planning of UNION ALL subqueries with output columns that are
not simple variables (Tom Lane)
Planning of such cases got noticeably worse in 9.1 as a result of a
misguided fix for "MergeAppend child's targetlist doesn't match
MergeAppend" errors. Revert that fix and do it another way.
* Fix slow session startup when pg_attribute is very large (Tom Lane)
If pg_attribute exceeds one-fourth of shared_buffers, cache
rebuilding code that is sometimes needed during session start would
trigger the synchronized-scan logic, causing it to take many times
longer than normal. The problem was particularly acute if many new
sessions were starting at once.
* Ensure sequential scans check for query cancel reasonably often
(Merlin Moncure)
A scan encountering many consecutive pages that contain no live
tuples would not respond to interrupts meanwhile.
* Ensure the Windows implementation of PGSemaphoreLock() clears
ImmediateInterruptOK before returning (Tom Lane)
This oversight meant that a query-cancel interrupt received later
in the same query could be accepted at an unsafe time, with
unpredictable but not good consequences.
* Show whole-row variables safely when printing views or rules (Abbas
Butt, Tom Lane)
Corner cases involving ambiguous names (that is, the name could be
either a table or column name of the query) were printed in an
ambiguous way, risking that the view or rule would be interpreted
differently after dump and reload. Avoid the ambiguous case by
attaching a no-op cast.
* Fix "COPY FROM" to properly handle null marker strings that
correspond to invalid encoding (Tom Lane)
A null marker string such as E'\\0' should work, and did work in
the past, but the case got broken in 8.4.
* Fix "EXPLAIN VERBOSE" for writable CTEs containing RETURNING
clauses (Tom Lane)
* Fix "PREPARE TRANSACTION" to work correctly in the presence of
advisory locks (Tom Lane)
Historically, "PREPARE TRANSACTION" has simply ignored any
session-level advisory locks the session holds, but this case was
accidentally broken in 9.1.
* Fix truncation of unlogged tables (Robert Haas)
* Ignore missing schemas during non-interactive assignments of
search_path (Tom Lane)
This re-aligns 9.1's behavior with that of older branches.
Previously 9.1 would throw an error for nonexistent schemas
mentioned in search_path settings obtained from places such as
"ALTER DATABASE SET".
* Fix bugs with temporary or transient tables used in extension
scripts (Tom Lane)
This includes cases such as a rewriting "ALTER TABLE" within an
extension update script, since that uses a transient table behind
the scenes.
* Ensure autovacuum worker processes perform stack depth checking
properly (Heikki Linnakangas)
Previously, infinite recursion in a function invoked by
auto-"ANALYZE" could crash worker processes.
* Fix logging collector to not lose log coherency under high load
(Andrew Dunstan)
The collector previously could fail to reassemble large messages if
it got too busy.
* Fix logging collector to ensure it will restart file rotation after
receiving SIGHUP (Tom Lane)
* Fix "too many LWLocks taken" failure in GiST indexes (Heikki
Linnakangas)
* Fix WAL replay logic for GIN indexes to not fail if the index was
subsequently dropped (Tom Lane)
* Correctly detect SSI conflicts of prepared transactions after a
crash (Dan Ports)
* Avoid synchronous replication delay when committing a transaction
that only modified temporary tables (Heikki Linnakangas)
In such a case the transaction's commit record need not be flushed
to standby servers, but some of the code didn't know that and
waited for it to happen anyway.
* Fix error handling in pg_basebackup (Thomas Ogrisegg, Fujii Masao)
* Fix walsender to not go into a busy loop if connection is
terminated (Fujii Masao)
* Fix memory leak in PL/pgSQL's "RETURN NEXT" command (Joe Conway)
* Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
function's first variable (Tom Lane)
* Ensure that PL/Perl package-qualifies the _TD variable (Alex
Hunsaker)
This bug caused trigger invocations to fail when they are nested
within a function invocation that changes the current package.
* Fix PL/Python functions returning composite types to accept a
string for their result value (Jan Urbanski)
This case was accidentally broken by the 9.1 additions to allow a
composite result value to be supplied in other formats, such as
dictionaries.
* Fix potential access off the end of memory in psql's expanded
display ("\x") mode (Peter Eisentraut)
* Fix several performance problems in pg_dump when the database
contains many objects (Jeff Janes, Tom Lane)
pg_dump could get very slow if the database contained many schemas,
or if many objects are in dependency loops, or if there are many
owned sequences.
* Fix memory and file descriptor leaks in pg_restore when reading a
directory-format archive (Peter Eisentraut)
* Fix pg_upgrade for the case that a database stored in a non-default
tablespace contains a table in the cluster's default tablespace
(Bruce Momjian)
* In ecpg, fix rare memory leaks and possible overwrite of one byte
after the sqlca_t structure (Peter Eisentraut)
* Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
connections upon error (Tom Lane)
* Fix "contrib/dblink" to report the correct connection name in error
messages (Kyotaro Horiguchi)
* Fix "contrib/vacuumlo" to use multiple transactions when dropping
many large objects (Tim Lewis, Robert Haas, Tom Lane)
This change avoids exceeding max_locks_per_transaction when many
objects need to be dropped. The behavior can be adjusted with the
new -l (limit) option.
* Update time zone data files to tzdata release 2012c for DST law
changes in Antarctica, Armenia, Chile, Cuba, Falkland Islands,
Gaza, Haiti, Hebron, Morocco, Syria, and Tokelau Islands; also
historical corrections for Canada.


☆ postgresql-9.0.8
http://www.postgresql.org/
http://ftp.postgresql.org/pub/source/v9.0.8/postgresql-9.0.8.tar.gz

Release 9.0.8

Release Date: 2012-06-04

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

Migration to Version 9.0.8

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

However, if you are upgrading from a version earlier than 9.0.6, see
the release notes for 9.0.6.
__________________________________________________________________

Changes

* Fix incorrect password transformation in "contrib/pgcrypto"'s DES
crypt() function (Solar Designer)
If a password string contained the byte value 0x80, the remainder
of the password was ignored, causing the password to be much weaker
than it appeared. With this fix, the rest of the string is properly
included in the DES hash. Any stored password values that are
affected by this bug will thus no longer match, so the stored
values may need to be updated. (CVE-2012-2143)
* Ignore SECURITY DEFINER and SET attributes for a procedural
language's call handler (Tom Lane)
Applying such attributes to a call handler could crash the server.
(CVE-2012-2655)
* Allow numeric timezone offsets in timestamp input to be up to 16
hours away from UTC (Tom Lane)
Some historical time zones have offsets larger than 15 hours, the
previous limit. This could result in dumped data values being
rejected during reload.
* Fix timestamp conversion to cope when the given time is exactly the
last DST transition time for the current timezone (Tom Lane)
This oversight has been there a long time, but was not noticed
previously because most DST-using zones are presumed to have an
indefinite sequence of future DST transitions.
* Fix text to name and char to name casts to perform string
truncation correctly in multibyte encodings (Karl Schnaitter)
* Fix memory copying bug in to_tsquery() (Heikki Linnakangas)
* Ensure txid_current() reports the correct epoch when executed in
hot standby (Simon Riggs)
* Fix planner's handling of outer PlaceHolderVars within subqueries
(Tom Lane)
This bug concerns sub-SELECTs that reference variables coming from
the nullable side of an outer join of the surrounding query. In
9.1, queries affected by this bug would fail with "ERROR:
Upper-level PlaceHolderVar found where not expected". But in 9.0
and 8.4, you'd silently get possibly-wrong answers, since the value
transmitted into the subquery wouldn't go to null when it should.
* Fix slow session startup when pg_attribute is very large (Tom Lane)
If pg_attribute exceeds one-fourth of shared_buffers, cache
rebuilding code that is sometimes needed during session start would
trigger the synchronized-scan logic, causing it to take many times
longer than normal. The problem was particularly acute if many new
sessions were starting at once.
* Ensure sequential scans check for query cancel reasonably often
(Merlin Moncure)
A scan encountering many consecutive pages that contain no live
tuples would not respond to interrupts meanwhile.
* Ensure the Windows implementation of PGSemaphoreLock() clears
ImmediateInterruptOK before returning (Tom Lane)
This oversight meant that a query-cancel interrupt received later
in the same query could be accepted at an unsafe time, with
unpredictable but not good consequences.
* Show whole-row variables safely when printing views or rules (Abbas
Butt, Tom Lane)
Corner cases involving ambiguous names (that is, the name could be
either a table or column name of the query) were printed in an
ambiguous way, risking that the view or rule would be interpreted
differently after dump and reload. Avoid the ambiguous case by
attaching a no-op cast.
* Fix "COPY FROM" to properly handle null marker strings that
correspond to invalid encoding (Tom Lane)
A null marker string such as E'\\0' should work, and did work in
the past, but the case got broken in 8.4.
* Ensure autovacuum worker processes perform stack depth checking
properly (Heikki Linnakangas)
Previously, infinite recursion in a function invoked by
auto-"ANALYZE" could crash worker processes.
* Fix logging collector to not lose log coherency under high load
(Andrew Dunstan)
The collector previously could fail to reassemble large messages if
it got too busy.
* Fix logging collector to ensure it will restart file rotation after
receiving SIGHUP (Tom Lane)
* Fix WAL replay logic for GIN indexes to not fail if the index was
subsequently dropped (Tom Lane)
* Fix memory leak in PL/pgSQL's "RETURN NEXT" command (Joe Conway)
* Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
function's first variable (Tom Lane)
* Fix potential access off the end of memory in psql's expanded
display ("\x") mode (Peter Eisentraut)
* Fix several performance problems in pg_dump when the database
contains many objects (Jeff Janes, Tom Lane)
pg_dump could get very slow if the database contained many schemas,
or if many objects are in dependency loops, or if there are many
owned sequences.
* Fix pg_upgrade for the case that a database stored in a non-default
tablespace contains a table in the cluster's default tablespace
(Bruce Momjian)
* In ecpg, fix rare memory leaks and possible overwrite of one byte
after the sqlca_t structure (Peter Eisentraut)
* Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
connections upon error (Tom Lane)
* Fix "contrib/dblink" to report the correct connection name in error
messages (Kyotaro Horiguchi)
* Fix "contrib/vacuumlo" to use multiple transactions when dropping
many large objects (Tim Lewis, Robert Haas, Tom Lane)
This change avoids exceeding max_locks_per_transaction when many
objects need to be dropped. The behavior can be adjusted with the
new -l (limit) option.
* Update time zone data files to tzdata release 2012c for DST law
changes in Antarctica, Armenia, Chile, Cuba, Falkland Islands,
Gaza, Haiti, Hebron, Morocco, Syria, and Tokelau Islands; also
historical corrections for Canada.


☆ postgresql-8.4.12
http://www.postgresql.org/
http://ftp.postgresql.org/pub/source/v8.4.12/postgresql-8.4.12.tar.gz

Release 8.4.12

Release Date: 2012-06-04

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

Migration to Version 8.4.12

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

However, if you are upgrading from a version earlier than 8.4.10, see
the release notes for 8.4.10.
__________________________________________________________________

Changes

* Fix incorrect password transformation in "contrib/pgcrypto"'s DES
crypt() function (Solar Designer)
If a password string contained the byte value 0x80, the remainder
of the password was ignored, causing the password to be much weaker
than it appeared. With this fix, the rest of the string is properly
included in the DES hash. Any stored password values that are
affected by this bug will thus no longer match, so the stored
values may need to be updated. (CVE-2012-2143)
* Ignore SECURITY DEFINER and SET attributes for a procedural
language's call handler (Tom Lane)
Applying such attributes to a call handler could crash the server.
(CVE-2012-2655)
* Allow numeric timezone offsets in timestamp input to be up to 16
hours away from UTC (Tom Lane)
Some historical time zones have offsets larger than 15 hours, the
previous limit. This could result in dumped data values being
rejected during reload.
* Fix timestamp conversion to cope when the given time is exactly the
last DST transition time for the current timezone (Tom Lane)
This oversight has been there a long time, but was not noticed
previously because most DST-using zones are presumed to have an
indefinite sequence of future DST transitions.
* Fix text to name and char to name casts to perform string
truncation correctly in multibyte encodings (Karl Schnaitter)
* Fix memory copying bug in to_tsquery() (Heikki Linnakangas)
* Fix planner's handling of outer PlaceHolderVars within subqueries
(Tom Lane)
This bug concerns sub-SELECTs that reference variables coming from
the nullable side of an outer join of the surrounding query. In
9.1, queries affected by this bug would fail with "ERROR:
Upper-level PlaceHolderVar found where not expected". But in 9.0
and 8.4, you'd silently get possibly-wrong answers, since the value
transmitted into the subquery wouldn't go to null when it should.
* Fix slow session startup when pg_attribute is very large (Tom Lane)
If pg_attribute exceeds one-fourth of shared_buffers, cache
rebuilding code that is sometimes needed during session start would
trigger the synchronized-scan logic, causing it to take many times
longer than normal. The problem was particularly acute if many new
sessions were starting at once.
* Ensure sequential scans check for query cancel reasonably often
(Merlin Moncure)
A scan encountering many consecutive pages that contain no live
tuples would not respond to interrupts meanwhile.
* Ensure the Windows implementation of PGSemaphoreLock() clears
ImmediateInterruptOK before returning (Tom Lane)
This oversight meant that a query-cancel interrupt received later
in the same query could be accepted at an unsafe time, with
unpredictable but not good consequences.
* Show whole-row variables safely when printing views or rules (Abbas
Butt, Tom Lane)
Corner cases involving ambiguous names (that is, the name could be
either a table or column name of the query) were printed in an
ambiguous way, risking that the view or rule would be interpreted
differently after dump and reload. Avoid the ambiguous case by
attaching a no-op cast.
* Fix "COPY FROM" to properly handle null marker strings that
correspond to invalid encoding (Tom Lane)
A null marker string such as E'\\0' should work, and did work in
the past, but the case got broken in 8.4.
* Ensure autovacuum worker processes perform stack depth checking
properly (Heikki Linnakangas)
Previously, infinite recursion in a function invoked by
auto-"ANALYZE" could crash worker processes.
* Fix logging collector to not lose log coherency under high load
(Andrew Dunstan)
The collector previously could fail to reassemble large messages if
it got too busy.
* Fix logging collector to ensure it will restart file rotation after
receiving SIGHUP (Tom Lane)
* Fix WAL replay logic for GIN indexes to not fail if the index was
subsequently dropped (Tom Lane)
* Fix memory leak in PL/pgSQL's "RETURN NEXT" command (Joe Conway)
* Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
function's first variable (Tom Lane)
* Fix potential access off the end of memory in psql's expanded
display ("\x") mode (Peter Eisentraut)
* Fix several performance problems in pg_dump when the database
contains many objects (Jeff Janes, Tom Lane)
pg_dump could get very slow if the database contained many schemas,
or if many objects are in dependency loops, or if there are many
owned sequences.
* Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
connections upon error (Tom Lane)
* Fix "contrib/dblink" to report the correct connection name in error
messages (Kyotaro Horiguchi)
* Update time zone data files to tzdata release 2012c for DST law
changes in Antarctica, Armenia, Chile, Cuba, Falkland Islands,
Gaza, Haiti, Hebron, Morocco, Syria, and Tokelau Islands; also
historical corrections for Canada.


☆ postgresql-8.3.19
http://www.postgresql.org/
http://ftp.postgresql.org/pub/source/v8.3.19/postgresql-8.3.19.tar.gz

Release 8.3.19

Release Date: 2012-06-04

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

Migration to Version 8.3.19

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

However, if you are upgrading from a version earlier than 8.3.17, see
the release notes for 8.3.17.
__________________________________________________________________

Changes

* Fix incorrect password transformation in "contrib/pgcrypto"'s DES
crypt() function (Solar Designer)
If a password string contained the byte value 0x80, the remainder
of the password was ignored, causing the password to be much weaker
than it appeared. With this fix, the rest of the string is properly
included in the DES hash. Any stored password values that are
affected by this bug will thus no longer match, so the stored
values may need to be updated. (CVE-2012-2143)
* Ignore SECURITY DEFINER and SET attributes for a procedural
language's call handler (Tom Lane)
Applying such attributes to a call handler could crash the server.
(CVE-2012-2655)
* Allow numeric timezone offsets in timestamp input to be up to 16
hours away from UTC (Tom Lane)
Some historical time zones have offsets larger than 15 hours, the
previous limit. This could result in dumped data values being
rejected during reload.
* Fix timestamp conversion to cope when the given time is exactly the
last DST transition time for the current timezone (Tom Lane)
This oversight has been there a long time, but was not noticed
previously because most DST-using zones are presumed to have an
indefinite sequence of future DST transitions.
* Fix text to name and char to name casts to perform string
truncation correctly in multibyte encodings (Karl Schnaitter)
* Fix memory copying bug in to_tsquery() (Heikki Linnakangas)
* Fix slow session startup when pg_attribute is very large (Tom Lane)
If pg_attribute exceeds one-fourth of shared_buffers, cache
rebuilding code that is sometimes needed during session start would
trigger the synchronized-scan logic, causing it to take many times
longer than normal. The problem was particularly acute if many new
sessions were starting at once.
* Ensure sequential scans check for query cancel reasonably often
(Merlin Moncure)
A scan encountering many consecutive pages that contain no live
tuples would not respond to interrupts meanwhile.
* Ensure the Windows implementation of PGSemaphoreLock() clears
ImmediateInterruptOK before returning (Tom Lane)
This oversight meant that a query-cancel interrupt received later
in the same query could be accepted at an unsafe time, with
unpredictable but not good consequences.
* Show whole-row variables safely when printing views or rules (Abbas
Butt, Tom Lane)
Corner cases involving ambiguous names (that is, the name could be
either a table or column name of the query) were printed in an
ambiguous way, risking that the view or rule would be interpreted
differently after dump and reload. Avoid the ambiguous case by
attaching a no-op cast.
* Ensure autovacuum worker processes perform stack depth checking
properly (Heikki Linnakangas)
Previously, infinite recursion in a function invoked by
auto-"ANALYZE" could crash worker processes.
* Fix logging collector to not lose log coherency under high load
(Andrew Dunstan)
The collector previously could fail to reassemble large messages if
it got too busy.
* Fix logging collector to ensure it will restart file rotation after
receiving SIGHUP (Tom Lane)
* Fix PL/pgSQL's "GET DIAGNOSTICS" command when the target is the
function's first variable (Tom Lane)
* Fix several performance problems in pg_dump when the database
contains many objects (Jeff Janes, Tom Lane)
pg_dump could get very slow if the database contained many schemas,
or if many objects are in dependency loops, or if there are many
owned sequences.
* Fix "contrib/dblink"'s dblink_exec() to not leak temporary database
connections upon error (Tom Lane)
* Update time zone data files to tzdata release 2012c for DST law
changes in Antarctica, Armenia, Chile, Cuba, Falkland Islands,
Gaza, Haiti, Hebron, Morocco, Syria, and Tokelau Islands; also
historical corrections for Canada.

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


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




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