Re: New News Entry - Mailing list pgsql-www

From Andreas Grabmüller
Subject Re: New News Entry
Date
Msg-id 20031223145312.1905.qmail@osiris.gamecrashnet.de
Whole thread Raw
In response to New News Entry  (www@www.postgresql.com (World Wide Web Owner))
Responses Re: New News Entry  (Robert Treat <xzilla@users.sourceforge.net>)
List pgsql-www
Shouldn't it be mirrors-ftp.html instead of mirrors-www.html?

Mit freundlichen Grüßen
Andreas Grabmüller

----- Original-Nachricht -----
Von: "www@www.postgresql.com (World Wide Web" <www@www.postgresql.com>
An: pgsql-www@postgresql.org
Datum: Tuesday, December 23, 2003 03:32 PM
Betreff: [pgsql-www] New News Entry

> A new entry has been added to the news database.
>
> Database Admin: http://www.postgresql.org/admin/edit_news.php?169
>
> Submitted by: press@postgresql.org
> Headline: PostgreSQL 7.4.1 Released
> Summary:
>
> Its been almost 4 weeks since PostgreSQL 7.4 was released, and, as with
> all new releases, several bugs have been identified as administrators
> migrate their production databases up from older releases.
>
>
> Story:
>
> Its been almost 4 weeks since PostgreSQL 7.4 was released, and, as with
> all new releases, several bugs have been identified as administrators
> migrate their production databases up from older releases.
>
> As the list of Changes since 7.4 is fairly small, they are included in
> this email:
>
>      * Fixed bug in \"CREATE SCHEMA\" parsing in ECPG (Michael)
>      * Fix compile error when \"--enable-thread-safety\" and \"--with-perl\"
>        are used together (Peter)
>      * Fix for subqueries that used hash joins (Tom)
>      * Fix free space map compaction bug (Tom)
>      * Fix for Borland compiler build of libpq (Bruce)
>      * Fix netmask() and hostmask() to return the maximum-length masklen
>        (Tom)
>      * Several \"contrib/pg_autovacuum\" fixes
>      * Allow compile of \"contrib/cube\" under Cygwin (Jason Tishler)
>      * Fix Solaris use of password file when no passwords are defined
>        (Tom)
>      * JDBC fix for thread problems, other fixes
>      * Fix for bytea index lookups (Joe)
>      * Fix information schema for bit data types (Peter)
>      * Force zero_damaged_pages to be on during recovery from WAL
>      * Prevent some obscure cases of \"variable not in subplan target
>        lists\"
>      * Make PQescapeBytea and byteaout consistent with each other (Joe)
>      * Escape bytea output for bytes > 0x7e(Joe)
>      * Added missing SPI_finish() calls to dblink\'s
>        get_tuple_of_interest() (Joe)
>      * New Czech FAQ
>      * Fix information schema view constraint_column_usage for foreign
>        keys (Peter)
>      * ECPG fixes (Michael)
>      * Fix bug with multiple IN subqueries and joins in the subqueries
>        (Tom)
>      * Alllow COUNT(\'x\') to work (Tom)
>      * Install ECPG include files for Informix compatibility into
>        separate directory (Peter)
>      * Fix SSL memory leak (Neil)
>      * Prevent \"pg_service.conf\" from using service name as default
>        dbname (Bruce)
>      * Fix local ident authentication on FreeBSD (Tom)
>
> This version, as with most minor versions, does not require a dump/reload
> to put into place.  That said, there are some changes to the information
> schema that require a DROP/reload of that *specific* schema ... please
> read the HISTORY file for instruction on how to do this.
>
> As always, this release is available on all our mirrors, viable at:
>
>         http://www.postgresql.org/mirrors-www.html
>
> And, thanks to David Fetter, is also available via BitTorrent at:
>
>         http://bt.postgresql.org
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
>       joining column's datatypes do not match

--
LetzPlay.de
| Freemail:       http://www.letzplay.de/mail
| Forenhosting: http://www.letzplay.de/foren

pgsql-www by date:

Previous
From: www@www.postgresql.com (World Wide Web Owner)
Date:
Subject: New News Entry
Next
From: Robert Treat
Date:
Subject: Re: New News Entry