Ubuntu

New upstream bug fix releases 8.3.6/8.1.16

Reported by Martin Pitt on 2009-02-06
6
Affects Status Importance Assigned to Milestone
postgresql-8.1 (Ubuntu)
Undecided
Unassigned
Dapper
Medium
Martin Pitt
Hardy
Undecided
Unassigned
Intrepid
Undecided
Unassigned
Jaunty
Undecided
Unassigned
postgresql-8.3 (Ubuntu)
Undecided
Martin Pitt
Dapper
Undecided
Unassigned
Hardy
Medium
Martin Pitt
Intrepid
Medium
Martin Pitt
Jaunty
Undecided
Martin Pitt

Bug Description

Binary package hint: postgresql-8.1

There are new PostgreSQL upstream microreleases for 7.4 to 8.3. According to the SRU microrelease exception, stable Ubuntu releases should get them:

  http://www.postgresql.org/docs/8.3/static/release-8-3-6.html
  http://www.postgresql.org/docs/8.1/static/release.html#RELEASE-8-1-16

I will stop updating gutsy with the new 8.2, since the fixes are not critical, and it will go EOL in 2 months.

Martin Pitt (pitti) on 2009-02-06
Changed in postgresql-8.1:
status: New → Invalid
status: New → Invalid
status: New → Invalid
Changed in postgresql-8.3:
status: New → Invalid
Martin Pitt (pitti) wrote :

dapper/8.1 uploaded to -proposed. Steve, can you please process those? Thanks!

Changed in postgresql-8.1:
assignee: nobody → pitti
importance: Undecided → Medium
status: New → In Progress
Martin Pitt (pitti) wrote :

Synced 8.3.6-1 to Jaunty.

Changed in postgresql-8.3:
assignee: nobody → pitti
status: New → Fix Released
Martin Pitt (pitti) wrote :

intrepid/8.3.6 uploaded to -proposed queue.

Changed in postgresql-8.3:
assignee: nobody → pitti
importance: Undecided → Medium
status: New → In Progress
assignee: nobody → pitti
importance: Undecided → Medium
status: New → In Progress
Colin Watson (cjwatson) wrote :

Accepted postgresql-8.3 into hardy-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in postgresql-8.3:
status: In Progress → Fix Committed
Colin Watson (cjwatson) wrote :

Accepted postgresql-8.3 into intrepid-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in postgresql-8.3:
status: In Progress → Fix Committed
Colin Watson (cjwatson) wrote :

Accepted postgresql-8.1 into dapper-proposed; please test and give feedback here. Please see https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in postgresql-8.1:
status: In Progress → Fix Committed
Leonel Nunez (leonelnunez) wrote :

Tested Hardy

Installs, works fine

Leonel Nunez (leonelnunez) wrote :

Tested Ubuntu Dapper

Installs and works fine

Leonel Nunez (leonelnunez) wrote :

Tested Ubuntu Intrepid

Installs works fine ..

Martin Pitt (pitti) wrote :

Thanks Leonel, your testing is highly appreciated!

I installed all the .debs from -proposed into my stable chroots and threw them at the postgresql-common test suite, which succeeded. The upstream test suite already runs during build.

So I consider those verified.

Launchpad Janitor (janitor) wrote :
Download full text (4.2 KiB)

This bug was fixed in the package postgresql-8.3 - 8.3.6-0ubuntu8.10

---------------
postgresql-8.3 (8.3.6-0ubuntu8.10) intrepid-proposed; urgency=low

  * New upstream bug fix release: (LP: #326372)
    - Make "DISCARD ALL" release advisory locks, in addition to
      everything it already did. This was decided to be the most
      appropriate behavior. This could affect existing applications,
      however.
    - Fix whole-index GiST scans to work correctly. This error could
      cause rows to be lost if a table is clustered on a GiST index.
    - Fix crash of xmlconcat(NULL).
    - Fix possible crash in ispell dictionary if high-bit-set characters
      are used as flags. This is known to be done by one widely
      available Norwegian dictionary, and the same condition may exist
      in others. (Closes: #513580)
    - Fix misordering of pg_dump output for composite types. The most
      likely problem was for user-defined operator classes to be
      dumped after indexes or views that needed them.
    - Improve handling of URLs in headline() function.
    - Improve handling of overlength headlines in headline() function.
    - Prevent possible Assert failure or misconversion if an encoding
      conversion is created with the wrong conversion function for the
      specified pair of encodings.
    - Fix possible Assert failure if a statement executed in PL/pgSQL is
      rewritten into another kind of statement, for example if an
      "INSERT" is rewritten into an "UPDATE".
    - Ensure that a snapshot is available to datatype input functions.
      This primarily affects domains that are declared with CHECK
      constraints involving user-defined stable or immutable functions.
      Such functions typically fail if no snapshot has been set.
    - Make it safer for SPI-using functions to be used within datatype
      I/O; in particular, to be used in domain check constraints.
    - Avoid unnecessary locking of small tables in "VACUUM".
    - Fix a problem that sometimes kept "ALTER TABLE ENABLE/DISABLE RULE"
      from being recognized by active sessions.
    - Fix a problem that made UPDATE RETURNING tableoid return zero
      instead of the correct OID.
    - Allow functions declared as taking ANYARRAY to work on the
      pg_statistic columns of that type.
      This used to work, but was unintentionally broken in 8.3.
    - Fix planner misestimation of selectivity when transitive equality
      is applied to an outer-join clause.
      This could result in bad plans for queries like ... from a left
      join b on a.a1 = b.b1 where a.a1 = 42 ...
    - Improve optimizer's handling of long IN lists. This change
      avoids wasting large amounts of time on such lists when
      constraint exclusion is enabled.
    - Prevent synchronous scan during GIN index build. Because GIN is
      optimized for inserting tuples in increasing TID order, choosing
      to use a synchronous scan could slow the build by a factor of
      three or more.
    - Ensure that the contents of a holdable cursor don't depend on the
      contents of TOAST tables. Previously, large field values in a
      cursor result might be represented as TOAST poi...

Read more...

Changed in postgresql-8.3:
status: Fix Committed → Fix Released
Launchpad Janitor (janitor) wrote :
Download full text (4.2 KiB)

This bug was fixed in the package postgresql-8.3 - 8.3.6-0ubuntu8.04

---------------
postgresql-8.3 (8.3.6-0ubuntu8.04) hardy-proposed; urgency=low

  * New upstream bug fix release: (LP: #326372)
    - Make "DISCARD ALL" release advisory locks, in addition to
      everything it already did. This was decided to be the most
      appropriate behavior. This could affect existing applications,
      however.
    - Fix whole-index GiST scans to work correctly. This error could
      cause rows to be lost if a table is clustered on a GiST index.
    - Fix crash of xmlconcat(NULL).
    - Fix possible crash in ispell dictionary if high-bit-set characters
      are used as flags. This is known to be done by one widely
      available Norwegian dictionary, and the same condition may exist
      in others. (Closes: #513580)
    - Fix misordering of pg_dump output for composite types. The most
      likely problem was for user-defined operator classes to be
      dumped after indexes or views that needed them.
    - Improve handling of URLs in headline() function.
    - Improve handling of overlength headlines in headline() function.
    - Prevent possible Assert failure or misconversion if an encoding
      conversion is created with the wrong conversion function for the
      specified pair of encodings.
    - Fix possible Assert failure if a statement executed in PL/pgSQL is
      rewritten into another kind of statement, for example if an
      "INSERT" is rewritten into an "UPDATE".
    - Ensure that a snapshot is available to datatype input functions.
      This primarily affects domains that are declared with CHECK
      constraints involving user-defined stable or immutable functions.
      Such functions typically fail if no snapshot has been set.
    - Make it safer for SPI-using functions to be used within datatype
      I/O; in particular, to be used in domain check constraints.
    - Avoid unnecessary locking of small tables in "VACUUM".
    - Fix a problem that sometimes kept "ALTER TABLE ENABLE/DISABLE RULE"
      from being recognized by active sessions.
    - Fix a problem that made UPDATE RETURNING tableoid return zero
      instead of the correct OID.
    - Allow functions declared as taking ANYARRAY to work on the
      pg_statistic columns of that type.
      This used to work, but was unintentionally broken in 8.3.
    - Fix planner misestimation of selectivity when transitive equality
      is applied to an outer-join clause.
      This could result in bad plans for queries like ... from a left
      join b on a.a1 = b.b1 where a.a1 = 42 ...
    - Improve optimizer's handling of long IN lists. This change
      avoids wasting large amounts of time on such lists when
      constraint exclusion is enabled.
    - Prevent synchronous scan during GIN index build. Because GIN is
      optimized for inserting tuples in increasing TID order, choosing
      to use a synchronous scan could slow the build by a factor of
      three or more.
    - Ensure that the contents of a holdable cursor don't depend on the
      contents of TOAST tables. Previously, large field values in a
      cursor result might be represented as TOAST pointe...

Read more...

Changed in postgresql-8.3:
status: Fix Committed → Fix Released
Martin Pitt (pitti) wrote :

Copied to dapper-updates, too.

Changed in postgresql-8.1:
status: Fix Committed → Fix Released
Leonel Nunez (leonelnunez) wrote :

I saw the new packages ready on the repositories and I've upgaded some servers

Just asking : why there was no announce in
www.ubuntu.com/usn and
https://lists.ubuntu.com/archives/ubuntu-security-announce/2009-February/thread.html
for the new packages ??

Thank you

Leonel Nunez [2009-02-19 12:28 -0000]:
> Just asking : why there was no announce in
> www.ubuntu.com/usn and
> https://lists.ubuntu.com/archives/ubuntu-security-announce/2009-February/thread.html
> for the new packages ??

They do not fix security holes, and did not go to hardy-security. They
just fix some bugs and thus went to hardy-updates. Bug fix updates are
not announced separately, since they are already documented in the
bug reports (every change log refers to a bug report with details).

Leonel Nunez (leonelnunez) wrote :

Thank you

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers