returned by getaddrinfo_all will have enough room for an IPv6 address.

that have IPv4-embedded-in-IPv6 addresses.  Per idea of Andreas Pflug.

< * Allow psql to do table completion for SELECT * FROM schema_part and
> * -Allow psql to do table completion for SELECT * FROM schema_part and

Needed for libpq builds, not just for native Win32 port, and probably
for cygwin too.

--
Alvaro Herrera (<alvherre[a]dcc.uchile.cl>)

Andrew Dunstan

> * Maintain a map of recently-expired of pages so vacuum can reclaim
>   free space without a sequential scan

> * -Improve concurrency of hash indexes (Tom)

platform.

Andreas Pflug

> 	o Allow ALTER TABLE ... ALTER CONSTRAINT ... RENAME

<
> * Print table names with constraint names in error messages, or make constraint
>   names unique within a schema

pghackers.  This fixes the problem recently reported by Markus KrÌutner
(hash bucket split corrupts the state of scans being done concurrently),
and I believe it also fixes all the known problems with deadlocks in
hash index operations.  Hash indexes are still not really ready for prime
time (since they aren't WAL-logged), but this is a step forward.

grantees.

administrator has not turned it on, and fix other PGC_USERLIMIT
variables.

> * Allow to_char to print localized month names (Karel)

bound is valid but does nothing.

suggested by Richard Huxton <dev@archonet.com>

accordingly.

* -Have standalone backend read postgresql.conf (Tom)

Ian Barwick

From Karel Zak.

killed items; just skip to the next item immediately.  Only check for
key equality when we reach a non-killed item or the end of the index
page.  This saves key comparisons when there are lots of killed items,
as for example in a heavily-updated table that's not been vacuumed lately.
Seems to be a win for pgbench anyway.

config file if it exists.  This was already discussed as being a good
idea, and now seems the cleanest way to deal with initdb-time failures
on machines with small SHMMAX.  (The submitted patches instead modified
initdb.sh to pass the correct sizing parameters, but that would still
leave standalone backends prone to failure later.  An admin who needs
to use a standalone backend has enough trouble already, he shouldn't
have to manually configure its shmem settings...)