Skip site navigation (1) Skip section navigation (2)

== PostgreSQL Weekly News - July 6th 2004 ==

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: pgsql-announce(at)postgresql(dot)org
Subject: == PostgreSQL Weekly News - July 6th 2004 ==
Date: 2004-07-07 03:59:22
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-announce
== PostgreSQL Weekly News - July 6th 2004 ==

        Having passed the July 1st deadline, we are now officially in feature 
freeze. That means that any patches that introduce new features will be held 
off until the next development cycle. What type of patches will be accepted? 
Bugfixes, clean up of loose ends on new features, and documentation 
improvements are all welcome. The core team is currently targetting July 15th 
for the first official beta release, but we'll keep you posted as development 

        Several outstanding patches were committed this week as the 
patch-queue was cleared out. The fuzzymatch module in contrib added double 
metaphone code, and metaphone was changed so that an empty input string 
causes an empty output string to be returned rather than toss an ERROR. 
Operators for interval-plus-datetime were fleshed out for better SQL 
compliance. Two procedural languages received updates this week as well. The 
first involved a changing in the parsing of FOR loops in plpgsql so that the 
integer-loop-vs-query-loop decision is driven off the presence of '..' 
between IN and LOOP, rather than the presence of a matching record/row 
variable name. This means that the general error for mistyped record 
variables will now give a more meaningful error message than one referencing 
'..'. The other involved several upgrades to the plperl module thanks to the 
folks at Command Prompt and several developers who organized themselves on  New functionality includes shared data and namespace 
support, trigger support, support for returning records, spi_exec 
functionality, and the ability to return "record" and "setof record".

        So what else will be in this next release?  With the caveat that these 
features could be removed during the beta cycle, most of the big name 
features made it in under the wire including nested transactions, PITR, and 
integrated pg_autovacuum. It is also worth reminding folks about win32 
support, tablespace support, and the ARC buffer code, which is making this 
release one of the most significant in several years. Stay tuned as beta 
progress for updates on these features and a complete list of changes due in 
the next version of PostgreSQL.

== PostgreSQL Product News ==
Slony 1.0.0 Released
                                                                        introduces free PostgreSQL hosting

== PostgreSQL In the News ==
Fujitsu foots the bill for new PostgreSQL database features
FAQ on when to use "for update" in a query
Relational Databases Rule the Roost
Connect Computing Gives User a Linux Option
Why Write PostgreSQL Extension Functions?

== Upcoming Events ==
OSCon: Portland, OR, USA: July 26-30
There will be a PostgreSQL Track with many community members participating.
Linux World Expo: San Francisco, CA, USA: August 3-5
PostgreSQL will have a booth and B.O.F with OSDL.

== PostgreSQL Weekly News - July 6th 2004 ==
Don't forget to read Elein Mustain's Weekly Summary of the PostgreSQL
General Mailing List
On the Web:

pgsql-announce by date

Next:From: Joerg BudischewskiDate: 2004-07-11 10:35:00
Subject: Announcing postgresql-sdbc-0.6.1 driver of
Previous:From: Murray CummingDate: 2004-07-02 18:26:02
Subject: ANNOUNCE: Glom 0.8.5

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group