NOTICE: This package has been removed from pkgsrc

./databases/postgresql81-pltcl, PL/Tcl procedural language for the PostgreSQL backend

[ CVSweb ] [ Homepage ] [ RSS ] [ Required by ]


Branch: CURRENT, Version: 8.1.15, Package name: postgresql81-pltcl-8.1.15, Maintainer: jlam

PL/Tcl is a dynamic loadable extension for the PostgreSQL database system
that enables the Tcl language to be used to create functions and
trigger-procedures. It offers most of the capabilities a function
writer has in the C language.


Required to run:
[databases/postgresql81-client] [databases/postgresql81-server] [lang/tcl]

Required to build:
[devel/gmake] [devel/libtool-base] [devel/bison]

Master sites: (Expand)

SHA1: 7cb1d9278b9ce6352aef898b23e3191d3bd0bed0
RMD160: b4ca7376dac1b6d5b9b01801d38809661bee46f9
Filesize: 11499.202 KB

Version history: (Expand)


CVS history: (Expand)


   2008-06-20 10:27:58 by Adam Ciarcinski | Files touched by this commit (12) | Package updated
Log message:
Changes 8.1.13:
* Make pg_get_ruledef() parenthesize negative constants (Tom)
  Before this fix, a negative constant in a view or rule might be
  dumped as, say, -42::integer, which is subtly incorrect: it should
  be (-42)::integer due to operator precedence rules. Usually this
  would make little difference, but it could interact with another
  recent patch to cause PostgreSQL to reject what had been a valid
  "SELECT DISTINCT" view query. Since this could result in pg_dump
  output failing to reload, it is being treated as a high-priority
  fix. The only released versions in which dump output is actually
  incorrect are 8.3.1 and 8.2.7.
* Make "ALTER AGGREGATE ... OWNER TO" update pg_shdepend (Tom)
  This oversight could lead to problems if the aggregate was later
  involved in a "DROP OWNED" or "REASSIGN OWNED" operation.
   2008-06-12 04:14:58 by Joerg Sonnenberger | Files touched by this commit (1134)
Log message:
Add DESTDIR support.
   2008-01-18 06:06:45 by Tobias Nygren | Files touched by this commit (191)
Log message:
Per the process outlined in revbump(1), perform a recursive revbump
on packages that are affected by the switch from the openssl 0.9.7
branch to the 0.9.8 branch. ok jlam@
   2007-01-08 19:55:39 by Adam Ciarcinski | Files touched by this commit (12)
Log message:
Changes 8.1.6:
* Improve handling of getaddrinfo() on AIX
  This fixes a problem with starting the statistics collector, among
  other things.
* Fix pg_restore to handle a tar-format backup that contains large
  objects (blobs) with comments
* Fix "failed to re-find parent key" errors in "VACUUM"
* Clean out "pg_internal.init" cache files during server restart
  This avoids a hazard that the cache files might contain stale data
  after PITR recovery.
* Fix race condition for truncation of a large relation across a
  gigabyte boundary by "VACUUM"
* Fix bug causing needless deadlock errors on row-level locks
* Fix bugs affecting multi-gigabyte hash indexes
* Fix possible deadlock in Windows signal handling
* Fix error when constructing an ARRAY[] made up of multiple empty
  elements
* Fix ecpg memory leak during connection
* Fix for Darwin (OS X) compilation
* to_number() and to_char(numeric) are now STABLE, not IMMUTABLE, for
  new initdb installs
  This is because lc_numeric can potentially change the output of
  these functions.
* Improve index usage of regular expressions that use parentheses
  This improves psql \d performance also.
* Update timezone database
  This affects Australian and Canadian daylight-savings rules in
  particular.
   2006-03-21 07:39:33 by Martti Kuparinen | Files touched by this commit (8)
Log message:
s/wip/databases/ (hi uebayasi!)
   2006-03-20 15:45:52 by Masao Uebayashi | Files touched by this commit (42) | Imported package
Log message:
Initial import of PostgreSQL 8.1.3, from pkgsrc-wip.

This is an overview of new features in 8.1.0 against 8.0.x.  8.1.3 includes
many bug fixes since 8.1.0.  Please read documentation of the detailed changes
and procedure of data migration.

Overview

   Major changes in this release:

   Improve concurrent access to the shared buffer cache (Tom)
          Access to the shared buffer cache was identified as a
          significant scalability problem, particularly on multi-CPU
          systems. In this release, the way that locking is done in the
          buffer manager has been overhauled to reduce lock contention and
          improve scalability. The buffer manager has also been changed to
          use a "clock sweep" replacement policy.

   Allow index scans to use an intermediate in-memory bitmap (Tom)
          In previous releases, only a single index could be used to do
          lookups on a table. With this feature, if a query has "WHERE
          tab.col1 = 4 and tab.col2 = 9", and there is no multicolumn
          index on col1 and col2, but there is an index on col1 and
          another on col2, it is possible to search both indexes and
          combine the results in memory, then do heap fetches for only the
          rows matching both the col1 and col2 restrictions. This is very
          useful in environments that have a lot of unstructured queries
          where it is impossible to create indexes that match all possible
          access conditions. Bitmap scans are useful even with a single
          index, as they reduce the amount of random access needed; a
          bitmap index scan is efficient for retrieving fairly large
          fractions of the complete table, whereas plain index scans are
          not.

   Add two-phase commit (Heikki Linnakangas, Alvaro, Tom)
          Two-phase commit allows transactions to be "prepared" on several
          computers, and once all computers have successfully prepared
          their transactions (none failed), all transactions can be
          committed. Even if a machine crashes after a prepare, the
          prepared transaction can be committed after the machine is
          restarted. New syntax includes "PREPARE TRANSACTION" and
          "COMMIT/ROLLBACK PREPARED". A new system view pg_prepared_xacts
          has also been added.

   Create a new role system that replaces users and groups (Stephen Frost)
          Roles are a combination of users and groups. Like users, they
          can have login capability, and like groups, a role can have
          other roles as members. Roles basically remove the distinction
          between users and groups. For example, a role can:

          + Have login capability (optionally)
          + Own objects
          + Hold access permissions for database objects
          + Inherit permissions from other roles it is a member of

          Once a user logs into a role, she obtains capabilities of the
          login role plus any inherited roles, and can use "SET ROLE" to
          switch to other roles she is a member of. This feature is a
          generalization of the SQL standard's concept of roles. This
          change also replaces pg_shadow and pg_group by new role-capable
          catalogs pg_authid and pg_auth_members. The old tables are
          redefined as read-only views on the new role tables.

   Automatically use indexes for MIN() and MAX() (Tom)
          In previous releases, the only way to use an index for MIN() or
          MAX() was to rewrite the query as "SELECT col FROM tab ORDER BY
          col LIMIT 1". Index usage now happens automatically.

   Move /contrib/pg_autovacuum into the main server (Alvaro)
          Integrating autovacuum into the server allows it to be
          automatically started and stopped in sync with the database
          server, and allows autovacuum to be configured from
          "postgresql.conf".

   Add shared row level locks using SELECT ... FOR SHARE (Alvaro)
          While PostgreSQL's MVCC locking allows "SELECT" to never be
          blocked by writers and therefore does not need shared row locks
          for typical operations, shared locks are useful for applications
          that require shared row locking. In particular this reduces the
          locking requirements imposed by referential integrity checks.

   Add dependencies on shared objects, specifically roles (Alvaro)
          This extension of the dependency mechanism prevents roles from
          being dropped while there are still database objects they own.
          Formerly it was possible to accidentally "orphan" objects by
          deleting their owner. While this could be recovered from, it was
          messy and unpleasant.

   Improve performance for partitioned tables (Simon)
          The new constraint_exclusion configuration parameter avoids
          lookups on child tables where constraints indicate that no
          matching rows exist in the child table.

          This allows for a basic type of table partitioning. If child
          tables store separate key ranges and this is enforced using
          appropriate "CHECK" constraints, the optimizer will skip child
          table accesses when the constraint guarantees no matching rows
          exist in the child table.