postgresql-contrib-8.3 package is missing intarray

Bug #250483 reported by randomjunk
4
Affects Status Importance Assigned to Milestone
postgresql-8.3 (Ubuntu)
Fix Released
Undecided
Martin Pitt

Bug Description

Binary package hint: postgresql-contrib-8.3

The description for this package claims the intarray module is included, but when installed the module is not present.

From standard documentation it should be at /usr/share/postgresql/8.3/contrib/intarray.sql

Actually, I think it may have been renamed _int.sql which seems a bit random. Is there a good reason for this?

Revision history for this message
Martin Pitt (pitti) wrote :

Fixed in trunk.

Changed in postgresql-8.3:
assignee: nobody → pitti
status: New → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (5.1 KiB)

This bug was fixed in the package postgresql-8.3 - 8.3.4-1ubuntu1

---------------
postgresql-8.3 (8.3.4-1ubuntu1) intrepid; urgency=low

  * Upload current Debian bzr head to intrepid to get back in sync with
    Debian.
  * debian/rules: Enable hardening when we build on Ubuntu. Lenny is too close
    to release, so we do not enable that yet for Debian. Add hardening-wrapper
    and lsb-release build dependencies for this.

postgresql-8.3 (8.3.4-1) unstable; urgency=low

  * New upstream bugfix release:
    - Fix bug in btree WAL recovery code. Recovery failed if the WAL ended
      partway through a page split operation.
    - Fix potential use of wrong cutoff XID for HOT page pruning.
      This error created a risk of corruption in system catalogs that are
      consulted by "VACUUM": dead tuple versions might be removed too
      soon. The impact of this on actual database operations would be
      minimal, since the system doesn't follow MVCC rules while examining
      catalogs, but it might result in transiently wrong output from
      pg_dump or other client programs.
    - Fix potential miscalculation of datfrozenxid.
    - Fix incorrect HOT updates after pg_class is reindexed.
      Corruption of pg_class could occur if REINDEX TABLE pg_class was
      followed in the same session by an ALTER TABLE RENAME or ALTER
      TABLE SET SCHEMA command.
    - Fix missed "combo cid" case. This error made rows incorrectly invisible
      to a transaction in which they had been deleted by multiple
      subtransactions that all aborted.
    - Prevent autovacuum from crashing if the table it's currently
      checking is deleted at just the wrong time.
    - Widen local lock counters from 32 to 64 bits. This responds to reports
      that the counters could overflow in sufficiently long transactions,
      leading to unexpected "lock is already held" errors.
    - Fix possible duplicate output of tuples during a GiST index scan.
    - Regenerate foreign key checking queries from scratch when either
      table is modified. Previously, 8.3 would attempt to replan the query,
      but would work from previously generated query text. This led to
      failures if a table or column was renamed.
    - Fix missed permissions checks when a view contains a simple UNION
      ALL construct. Permissions for the referenced tables were checked
      properly, but not permissions for the view itself.
    - Add checks in executor startup to ensure that the tuples produced
      by an "INSERT" or "UPDATE" will match the target table's current
      rowtype. This situation is believed to be impossible in 8.3, but it can
      happen in prior releases, so a check seems prudent.
    - Fix possible repeated drops during "DROP OWNED". This would typically
      result in strange errors such as "cache lookup failed for relation NNN".
    - Fix several memory leaks in XML operations.
    - Fix xmlserialize() to raise error properly for unacceptable target
      data type.
    - Fix a couple of places that mis-handled multibyte characters in
      text search configuration file parsing. Certain characters occurring in
      configuration files would always cause "i...

Read more...

Changed in postgresql-8.3:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.