| Age | Commit message (Collapse) | Author |
|---|
|
> * -Allow user-defined types to accept 'typmod' parameters
|
|
>
> * Make consistent use of long/short command options --- pg_ctl needs
> long ones, pg_config doesn't have short ones, postgres doesn't have
> enough long ones, etc.
|
|
> 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
|
|
|
|
|
|
back-stamped for this.
|
|
|
|
|
|
|
|
provide a switch for similar behaviour in pg_ctl.
|
|
|
|
|
|
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.
|
|
about typmod representation for standard types out into type-specific
typmod I/O functions. Teodor Sigaev, with some editorialization by
Tom Lane.
|
|
|
|
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg01213.php
|
|
< * Add a GUC to control whether BEGIN inside a transcation should abort
< the transaction.
|
|
for use with constraint exclusion. We can prove those cases now...
|
|
< * Move some /contrib modules out to their own project sites
<
< Particularly, move GPL-licensed /contrib/userlock and
< /contrib/dbmirror/clean_pending.pl.
<
|
|
remove long-obsolete statement that there isn't a check for infinite
recursion in view rules.
|
|
|
|
|
|
the XmlExpr code in various lists, use a representation that has some hope
of reverse-listing correctly (though it's still a de-escaping function
shy of correctness), generally try to make it look more like Postgres
coding conventions.
|
|
and UPDATE are clearly covered by the term.
|
|
rather than being disallowed.
|
|
cases. Operator classes now exist within "operator families". While most
families are equivalent to a single class, related classes can be grouped
into one family to represent the fact that they are semantically compatible.
Cross-type operators are now naturally adjunct parts of a family, without
having to wedge them into a particular opclass as we had done originally.
This commit restructures the catalogs and cleans up enough of the fallout so
that everything still works at least as well as before, but most of the work
needed to actually improve the planner's behavior will come later. Also,
there are not yet CREATE/DROP/ALTER OPERATOR FAMILY commands; the only way
to create a new family right now is to allow CREATE OPERATOR CLASS to make
one by default. I owe some more documentation work, too. But that can all
be done in smaller pieces once this infrastructure is in place.
|
|
work effectively with open source communities.
|
|
added.
|
|
|
|
|
|
|
|
< o Improve xid wraparound detection by recording per-table rather
< than per-database
|
|
an = sign. Tom Lane and Andrew Dunstan.
|
|
operator strategy numbers, ie, GiST and GIN. This is almost cosmetic
enough to not need a catversion bump, but since the opr_sanity regression
test has to change in sync with the catalog entry, I figured I'd better
do one.
|
|
< While PostgreSQL clients runs fine limited-resource environments, the
> While PostgreSQL clients runs fine in limited-resource environments, the
|
|
< * Make CLUSTER preserve recently-dead tuples per MVCC requirements
> o Make CLUSTER preserve recently-dead tuples per MVCC requirements
|
|
properly.
Remove SGML docs about openjade performance patch, and instead add
comment in style sheet where indenting code is commented out.
Backpatch to 8.2.X.
|
|
>
> * Embedded server (not wanted)
>
> While PostgreSQL clients runs fine limited-resource environments, the
> server requires multiple processes and a stable pool of resources to
> run reliabily and efficiently. Stripping down the PostgreSQL server
> to run in the same process address space as the client application
> would add too much complexity and failure cases.
|
|
< * Consider changing documentation from SGML to XML
> * Consider changing documentation format from SGML to XML
< http://archives.postgresql.org/pgsql-docs/2006-12/msg00033.php
> http://archives.postgresql.org/pgsql-docs/2006-12/msg00152.php
|
|
>
> * Consider changing documentation from SGML to XML
>
> http://archives.postgresql.org/pgsql-docs/2006-12/msg00033.php
>
|
|
time.
|
|
|
|
correct, add comments about other multiple runs in the Makefile.
Backpatch to 8.2.X.
|
|
< * Have EXPLAIN ANALYZE highlight poor optimizer estimates
> * Have EXPLAIN ANALYZE issue NOTICE messages when the estimated and
> actual row counts differ by a specified percentage
|
|
|
|
< * Allow REINDEX CONCURRENTLY
|
