Next | Query returned 19 messages, browsing 1 to 10 | Previous

History of commit frequency

CVS Commit History:


   2009-08-15 07:57:26 by Thomas Klausner | Files touched by this commit (1)
Log message:
Remove postgresql81 removal remnant.
   2009-06-14 19:43:27 by Joerg Sonnenberger | Files touched by this commit (120)
Log message:
Remove @dirrm entries from PLISTs
   2009-05-16 09:22:04 by Roland Illig | Files touched by this commit (20)
Log message:
cleanup: replaced _PKG_SILENT and _PKG_DEBUG with RUN.
   2009-02-07 18:43:54 by Adam Ciarcinski | Files touched by this commit (6)
Log message:
Changes 8.1.16:
* Fix crash in autovacuum
  The crash occurs only after vacuuming a whole database for
  anti-transaction-wraparound purposes, which means that it occurs
  infrequently and is hard to track down.
* 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
* Avoid unnecessary locking of small tables in "VACUUM"
* Ensure that the contents of a holdable cursor don't depend on the
  contents of TOAST tables
* Fix uninitialized variables in "contrib/tsearch2"'s get_covers()
  function
* Fix configure script to properly report failure when unable to
  obtain linkage information for PL/Perl
* Make all documentation reference pgsql-bugs and/or pgsql-hackers as
  appropriate, instead of the now-decommissioned pgsql-ports and
  pgsql-patches mailing lists
* Update time zone data files to tzdata release 2009a (for Kathmandu
  and historical DST corrections in Switzerland, Cuba)
   2008-11-04 10:52:29 by Adam Ciarcinski | Files touched by this commit (5)
Log message:
Changes 8.1.15:
* Fix GiST index corruption due to marking the wrong index entry
  "dead" after a deletion.
  This would result in index searches failing to find rows they
  should have found.
* Fix backend crash when the client encoding cannot represent a
  localized error message.
  We have addressed similar issues before, but it would still fail if
  the "character has no equivalent" message itself couldn't be
  converted. The fix is to disable localization and send the plain
  ASCII error message when we detect such a situation.
* Fix possible crash when deeply nested functions are invoked from a
  trigger.
* Fix mis-expansion of rule queries when a sub-SELECT appears in a
  function call in FROM, a multi-row VALUES list, or a RETURNING list
* Ensure an error is reported when a newly-defined PL/pgSQL trigger
  function is invoked as a normal function.
* Prevent possible collision of relfilenode numbers when moving a
  table to another tablespace with "ALTER SET TABLESPACE".
  The command tried to re-use the existing filename, instead of
  picking one that is known unused in the destination directory.
* Fix incorrect tsearch2 headline generation when single query item
  matches first word of text.
* Fix improper display of fractional seconds in interval values when
  using a non-ISO datestyle in an "--enable-integer-datetimes" build
* Ensure SPI_getvalue and SPI_getbinval behave correctly when the
  passed tuple and tuple descriptor have different numbers of columns.
* Fix ecpg's parsing of "CREATE ROLE".
* Fix recent breakage of pg_ctl restart.
* Update time zone data files to tzdata release 2008i (for DST law
  changes in Argentina, Brazil, Mauritius, Syria)
   2008-10-06 11:46:31 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 8.1.14:
Bug-fix release, see HISTORY for details.
   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-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@
   2008-01-07 21:14:24 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 8.1.11:
This release contains a variety of fixes from 8.1.10, including fixes
for significant security issues.

This is the last 8.1.X release for which the PostgreSQL community will
produce binary packages for Windows. Windows users are encouraged to
move to 8.2.X or later, since there are Windows-specific fixes in 8.2.X
that are impractical to back-port. 8.1.X will continue to be supported
on other platforms.
   2007-09-19 22:01:59 by Adam Ciarcinski | Files touched by this commit (4)
Log message:
Changes 8.1.10:
* Prevent index corruption when a transaction inserts rows and then
  aborts close to the end of a concurrent "VACUUM" on the same table
* Make "CREATE DOMAIN ... DEFAULT NULL" work properly
* Allow the interval data type to accept input consisting only of
  milliseconds or microseconds
* Speed up rtree index insertion
* Fix excessive logging of SSL error messages
* Fix logging so that log messages are never interleaved when using
  the syslogger process
* Fix crash when log_min_error_statement logging runs out of memory
* Fix incorrect handling of some foreign-key corner cases
* Prevent "REINDEX" and "CLUSTER" from failing due to \ 
attempting to
  process temporary tables of other sessions
* Update the time zone database rules, particularly New Zealand's
  upcoming changes
* Windows socket improvements
* Suppress timezone name (%Z) in log timestamps on Windows because of
  possible encoding mismatches
* Require non-superusers who use "/contrib/dblink" to use only
  password authentication, as a security measure

Next | Query returned 19 messages, browsing 1 to 10 | Previous