> Second argument to metaphone is suposed to set the limit on the
> number of characters to return, but it breaks on some phrases:
>
> usps=# select metaphone(a,3),metaphone(a,4),metaphone(a,20) from
> (select 'Hello world'::varchar AS a) a;
> HLW       | HLWR      | HLWRLT
>
> usps=# select metaphone(a,3),metaphone(a,4),metaphone(a,20) from
> (select 'A A COMEAUX MEMORIAL'::varchar AS a) a;
  > AKM       | AKMKS     | AKMKSMMRL
>
> In every case I've found that does this, the 4th and 5th letters are
> always 'KS'.

Nice catch.

There was a bug in the original metaphone algorithm from CPAN. Patch
attached (while I was at it I updated my email address, changed the
copyright to PGDG, and removed an unnecessary palloc). Here's how it
looks now:

regression=# select metaphone(a,4) from (select 'A A COMEAUX
MEMORIAL'::varchar AS a) a;
   metaphone
-----------
   AKMK
(1 row)

regression=# select metaphone(a,5) from (select 'A A COMEAUX
MEMORIAL'::varchar AS a) a;
   metaphone
-----------
   AKMKS
(1 row)

Joe Conway

        Regression tests for IPv6 operations added.

        Documentation updated to document IPv6 bits.

        Stop treating IPv4 as an "unsigned int" and IPv6 as an array of
        characters.  Instead, always use the array of characters so we
        can have one function fits all.  This makes bitncmp(), addressOK(),
        and several other functions "just work" on both address families.

        add family() function which returns integer 4 or 6 for IPv4 or
        IPv6.  (See examples below)  Note that to add this new function
        you will need to dump/initdb/reload or find the correct magic
        to add the function to the postgresql function catalogs.

        IPv4 addresses always sort before IPv6.

        On disk we use AF_INET for IPv4, and AF_INET+1 for IPv6 addresses.
        This prevents the need for a dump and reload, but lets IPv6 parsing
        work on machines without AF_INET6.

        To select all IPv4 addresses from a table:

                select * from foo where family(addr) = 4 ...

        Order by and other bits should all work.

Michael Graff

< * Have SELECT '13 minutes'::interval display zero seconds
> * Have SELECT '13 minutes'::interval display zero seconds in ISO datestyle

> * Have SELECT '13 minutes'::interval display zero seconds

> * Allow the regression tests to start postmaster with -i so the tests
>   can be run on systems that don't support unix-domain sockets

> * Rename /scripts directory because they are all C programs now

<
> 	o Allow ALTER TABLE to modify column lengths and change to binary
> 	  compatible types

> * Modify pg_get_triggerdef() to take a boolean to pretty-print,
>  and use that as part of pg_dump along with psql
>

* Allow UPDATE, DELETE to handle table aliases for self-joins [delete]

> 	o Allow columns to be reordered using ALTER ... POSITION i col1 [,col2];
> 	  have SELECT * and INSERT honor such ordering

	#include <pwd.h>
	#include <netdb.h>

in MS CC/Borland builds.

it.

Also handle __ss_family as a synonym for ss_family.

Kurt Roeckx

> * Have initdb set DateStyle based on locale?

<   from making invalid dates valid?
>   from making invalid dates valid

just a preformatted message; per suggestion by Sean Chittenden.

Solaris with Open SSL version 0.9.7b

> * Exit postmaster if postgresql.conf can not be opened

	* Allow SSL-enabled clients to turn off SSL transfers

> * Change CVS $Id$ to $PostgreSQL$

specific hash functions used by hash indexes, rather than the old
not-datatype-aware ComputeHashFunc routine.  This makes it safe to do
hash joining on several datatypes that previously couldn't use hashing.
The sets of datatypes that are hash indexable and hash joinable are now
exactly the same, whereas before each had some that weren't in the other.

reasonable.

out of mind, because it'd been commented out years ago).  Try to bring the
remains up to a reasonable level of currency, and give it all approximately
the same high level of abstraction.

<   from making invalid dates valid
>   from making invalid dates valid?

> * Allow current datestyle to restrict dates;  prevent month/day swapping
>   from making invalid dates valid
> * Prevent month/day swapping of ISO dates to make invalid dates valid

regression test diffs...).

client applications.  Some editorial work on libpq.sgml, too.

a ReadyForQuery (Z message) immediately and then another one after the
Sync message arrives.  Suppress the first one to make it work per spec.