Re: Fw: Cual Instalar ?? 8.2.2 o 8.1.4 en CentOS4.4

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Jaime Rodríguez Molina <jr(dot)molina(at)wanadoo(dot)es>
Cc: Antonio Vivanco <avivanco(at)artel(dot)cl>, pgsql-es-ayuda(at)postgresql(dot)org
Subject: Re: Fw: Cual Instalar ?? 8.2.2 o 8.1.4 en CentOS4.4
Date: 2007-02-05 16:40:29
Message-ID: 20070205164029.GC7196@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-es-ayuda

Jaime Rodríguez Molina escribió:
> Antonio Vivanco wrote:
> >Estimados,
> >
> >Estoy montando una maquina (CentOs 4.4 ( = al RHES-4.4) ) y tengo la
> >duda de que vercion de postgres instalar.
> >En el sitio de CentOS tienen el RPM de la 8.1.4.1, lo que debiera
> >significar que esta bien probado que funciona.
> >Por otro lado en al portal http://www.postgresql.org/ftp/source/
> >van en la 8.2.2
> >La distro originalmente viene con una 7x...

Si ya estas usando la serie 8.1, usa 8.1.7, que tiene corregidos varios
errores que hay en 8.1.4. Es probable que entre los updates de Redhat
(y CentOS) hayan actualizaciones a 8.1.7 tambien ...

Si el sistema aun no empieza a usarse, te recomiendo 8.2.2.

Discrepo con la opinion de Jaime. Entre 8.1 y 8.2 si hay muchas
diferencias:

http://www.postgresql.org/docs/current/static/release-8-2.html

> >Este sistema atiende publico, asi que no puede tener problemas.
> >Que me recomiendan ??

Si el sistema "no puede tener problemas", entonces jamas debes usar una
version que no sea la ultima de su serie. Por ej. si usas 8.1.4 en
lugar de 8.1.7, cualquiera de los siguientes bugs te puede causar
problemas:

* Remove security vulnerabilities that allowed connected users to
read backend memory (Tom)

The vulnerabilities involve suppressing the normal check that a
SQL function returns the data type it's declared to, and changing the
data type of a table column (CVE-2007-0555, CVE-2007-0556). These errors
can easily be exploited to cause a backend crash, and in principle might
be used to read database content that the user should not be able to
access.

* Fix rare bug wherein btree index page splits could fail due to
choosing an infeasible split point (Heikki Linnakangas)
* Improve VACUUM performance for databases with many tables (Tom)
* Fix autovacuum to avoid leaving non-permanent transaction IDs in
non-connectable databases (Alvaro)

This bug affects the 8.1 branch only.
* Fix for rare Assert() crash triggered by UNION (Tom)
* Tighten security of multi-byte character processing for UTF8
sequences over three bytes long (Tom)
* Fix bogus "permission denied" failures occurring on Windows due to
attempts to fsync already-deleted files (Magnus, Tom)
* Fix possible crashes when an already-in-use PL/pgSQL function is
updated (Tom)

* Improve handling of getaddrinfo() on AIX (Tom)

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 (Tom)
* Fix "failed to re-find parent key" errors in VACUUM (Tom)
* Clean out pg_internal.init cache files during server restart
(Simon)

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 (Tom)
* Fix bug causing needless deadlock errors on row-level locks (Tom)
* Fix bugs affecting multi-gigabyte hash indexes (Tom)
* Fix possible deadlock in Windows signal handling (Teodor)
* Fix error when constructing an ARRAY[] made up of multiple empty
elements (Tom)
* Fix ecpg memory leak during connection (Michael)
* Fix for Darwin (OS X) compilation (Tom)
* to_number() and to_char(numeric) are now STABLE, not IMMUTABLE,
for new initdb installs (Tom)

This is because lc_numeric can potentially change the output of
these functions.
* Improve index usage of regular expressions that use parentheses
(Tom)

This improves psql \d performance also.
* Update timezone database

This affects Australian and Canadian daylight-savings rules in
particular.

* Disallow aggregate functions in UPDATE commands, except within
sub-SELECTs (Tom)

The behavior of such an aggregate was unpredictable, and in 8.1.X
could cause a crash, so it has been disabled. The SQL standard does not
allow this either.
* Fix core dump when an untyped literal is taken as ANYARRAY
* Fix core dump in duration logging for extended query protocol when
a COMMIT or ROLLBACK is executed
* Fix mishandling of AFTER triggers when query contains a SQL
function returning multiple rows (Tom)
* Fix ALTER TABLE ... TYPE to recheck NOT NULL for USING clause
(Tom)
* Fix string_to_array() to handle overlapping matches for the
separator string

For example, string_to_array('123xx456xxx789', 'xx').
* Fix to_timestamp() for AM/PM formats (Bruce)
* Fix autovacuum's calculation that decides whether ANALYZE is
needed (Alvaro)
* Fix corner cases in pattern matching for psql's \d commands
* Fix index-corrupting bugs in /contrib/ltree (Teodor)
* Numerous robustness fixes in ecpg (Joachim Wieland)
* Fix backslash escaping in /contrib/dbmirror
* Minor fixes in /contrib/dblink and /contrib/tsearch2
* Efficiency improvements in hash tables and bitmap index scans
(Tom)
* Fix instability of statistics collection on Win32 (Tom, Andrew)
* Fix statement_timeout to use the proper units on Win32 (Bruce)

In previous Win32 8.1.X versions, the delay was off by a factor of
100.
* Fixes for MSVC and Borland C++ compilers (Hiroshi Saito)
* Fixes for AIX and Intel compilers (Tom)
* Fix rare bug in continuous archiving (Tom)

--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Responses

Browse pgsql-es-ayuda by date

  From Date Subject
Next Message Marco Vinicio Jimenez Rojas 2007-02-05 16:40:52 consulta
Previous Message Yessica Brinkmann 2007-02-05 16:30:51 Re: Existe alguna función similar a DIFFERENCE() y SOUNDEX() de sql server en Postgres?