> 	o Consider parsing the -c string into individual queries so each
> 	  is run in its own transaction
>
> 	o Consider disallowing multiple queries in PQexec() as an
> 	  additional barrier to SQL injection attacks

< * Allow CREATE INDEX to take an additional parameter for use with
<   special index types

< * Allow inherited tables to inherit index, UNIQUE constraint, and primary
<   key, foreign key
< * UNIQUE INDEX on base column not honored on INSERTs/UPDATEs from
<   inherited table:  INSERT INTO inherit_table (unique_index_col) VALUES
<   (dup) should fail
<
<   The main difficulty with this item is the problem of creating an index
<   that can span more than one table.
<
< * Allow SELECT ... FOR UPDATE on inherited tables
> * Inheritance
>
> 	o Allow inherited tables to inherit indexes, UNIQUE constraints,
> 	  and primary/foreign keys
> 	o Honor UNIQUE INDEX on base column in INSERTs/UPDATEs
> 	  on inherited table, e.g.  INSERT INTO inherit_table
> 	  (unique_index_col) VALUES (dup) should fail
>
> 	  The main difficulty with this item is the problem of
> 	  creating an index that can span multiple tables.
>
> 	o Allow SELECT ... FOR UPDATE on inherited tables
>
>
>

> * -Allow the pg_xlog directory location to be specified during initdb

Euler Taveira de Oliveira

sets the items, and serializes the value back (rather than adding an
arbitrary number of XML preambles as before).

The libxml memory management via palloc had to be disabled because it
crashes when libxml tries to access memory that was helpfully freed
earlier by PostgreSQL.  This needs further thought.

properly when doing a lookahead.  The lack of this was causing various
interesting misbehaviors when one tries to use "with" as a plain identifier.

Improve release docs for ecpg regression tests.

like my HPPA ...

the library version number.

back-stamped for this.

Call setrlimit if possible in pg_regress to allow core file generation, and provide a switch for similar behaviour in pg_ctl.

Stefan Kaltenbrunner

database privileges from a pre-8.2 server.  This ensures that the reloaded
database will maintain the same behavior it had in the previous installation,
ie, everybody has connect privilege.  Per gripe from L Bayuk.

an optarg).  Add some comments noting that code in three different files has
to be kept in sync.  Fix erroneous description of -S switch (it sets work_mem
not silent_mode), and do some light copy-editing elsewhere in postgres-ref.

form '^(foo)$'.  Before, these could never be optimized into indexscans.
The recent changes to make psql and pg_dump generate such patterns (for \d
commands and -t and related switches, respectively) therefore represented
a big performance hit for people with large pg_class catalogs, as seen in
recent gripe from Erik Jones.  While at it, be more paranoid about
case-sensitivity checking in multibyte encodings, and fix some other
corner cases in which a regex might be interpreted too liberally.

document why this happens.  Remove exp() errno check because not needed.

having md.c return a success/failure boolean to smgr.c, which was just going
to elog anyway, let md.c issue the elog messages itself.  This allows better
error reporting, particularly in cases such as "short read" or "short write"
which Peter was complaining of.  Also, remove the kluge of allowing mdread()
to return zeroes from a read-beyond-EOF: this is now an error condition
except when InRecovery or zero_damaged_pages = true.  (Hash indexes used to
require that behavior, but no more.)  Also, enforce that mdwrite() is to be
used for rewriting existing blocks while mdextend() is to be used for
extending the relation EOF.  This restriction lets us get rid of the old
ad-hoc defense against creating huge files by an accidental reference to
a bogus block number: we'll only create new segments in mdextend() not
mdwrite() or mdread().  (Again, when InRecovery we allow it anyway, since
we need to allow updates of blocks that were later truncated away.)
Also, clean up the original makeshift patch for bug #2737: move the
responsibility for padding relation segments to full length into md.c.

only return Nan and set errno for pow/exp overflow/underflow.

platforms set errno, and we already have a check macro that detects
under/overflow, so there is no reason for platform-specific code
anymore.