| Age | Commit message (Collapse) | Author |
|---|
|
< stable logging probably can not have indexes. [wallog]
> stable logging probably can not have indexes. [walcontrol]
|
|
< STABLE | DEFAULT ]. [wallog]
> STABLE | DEFAULT ]. Tables using non-default logging should not use
> referential integrity with default-logging tables, and tables using
> stable logging probably can not have indexes. [wallog]
|
|
< the table. Another option is to avoid transaction logging entirely
< and truncate or drop the table on crash recovery. These should be
< implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
< TRUNCATE | STABLE | DEFAULT ]. [wallog]
> the table. This would affect COPY, and perhaps INSERT/UPDATE too.
> Another option is to avoid transaction logging entirely and truncate
> or drop the table on crash recovery. These should be implemented
> using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP | TRUNCATE |
> STABLE | DEFAULT ]. [wallog]
|
|
>
> * Allow control over which tables are WAL-logged
>
> Allow tables to bypass WAL writes and just fsync() dirty pages on
> commit. To do this, only a single writer can modify the table, and
> writes must happen only on new pages. Readers can continue accessing
> the table. Another option is to avoid transaction logging entirely
> and truncate or drop the table on crash recovery. These should be
> implemented using ALTER TABLE, e.g. ALTER TABLE PERSISTENCE [ DROP |
> TRUNCATE | STABLE | DEFAULT ]. [wallog]
|
|
|
|
< * %Remove behavior of postmaster -o after making postmaster/postgres
< flags unique
> * %Remove behavior of postmaster -o
|
|
|
|
|
|
http://archives.postgresql.org/pgsql-hackers/2006-01/msg00151.php for the
complete plan.
|
|
|
|
|
|
> * -Remove BeOS and QNX-specific code
|
|
|
|
|
|
> * Make CLUSTER preserve recently-dead tuples per MVCC requirements
|
|
< * Add missing rtree optimizer selectivity
> * Improve selectivity functions for geometric operators
|
|
documentation.
Michael Fuhr
|
|
|
|
< * Add missing optimizer selectivities for date, r-tree, etc
> * Add missing rtree optimizer selectivity
|
|
single column dump that has a \. value, so the load works properly. I
also added documentation describing this issue.
|
|
< * %Make row-wise comparisons work per SQL spec
> * -Make row-wise comparisons work per SQL spec
|
|
(previously we only did = and <> correctly). Also, allow row comparisons
with any operators that are in btree opclasses, not only those with these
specific names. This gets rid of a whole lot of indefensible assumptions
about the behavior of particular operators based on their names ... though
it's still true that IN and NOT IN expand to "= ANY". The patch adds a
RowCompareExpr expression node type, and makes some changes in the
representation of ANY/ALL/ROWCOMPARE SubLinks so that they can share code
with RowCompareExpr.
I have not yet done anything about making RowCompareExpr an indexable
operator, but will look at that soon.
initdb forced due to changes in stored rules.
|
|
and add logic to try max_fsm_pages up to 200000, plus accompanying minor
docs changes.
|
|
|
|
* %Make row-wise comparisons work per SQL spec
Right now, '(a, b) < (1, 2)' is processed as 'a < 1 and b < 2', but
the SQL standard requires it to be processed as a column-by-column
comparison, so the proper comparison is '(a < 1) OR (a = 1 AND b < 2)'.
|
|
|
|
|
|
|
|
postgresql.conf.sample too.
|
|
|
|
of having no password.
|
|
modify the previous \password patch to use it instead of depending
on a not-officially-exported function. Per discussion.
|
|
SET.
|
|
>
> A more complex solution would be to save multiple plans for different
> cardinality and use the appropriate plan based on the EXECUTE values.
>
|
|
|
|
Backpatch to 8.1.X.
|
|
Fix example for day and hours interval subtraction for new computation
method.
Update interval examples to display zero seconds, which is our default.
Backpatch to 8.1.X.
|
|
Per my recent proposal. I ended up basing the implementation on the
existing mechanism for enforcing valid join orders of IN joins --- the
rules for valid outer-join orders are somewhat similar.
|
|
|
|
password encryption. Also alter createuser command to the same effect.
|
|
< * Allow star join optimizations
<
< While our bitmap scan allows multiple indexes to be joined to get
< to heap rows, a star joins allows multiple dimension _tables_ to
< be joined to index into a larger main fact table. The join is
< usually performed by either creating a cartesian product of all
< the dimmension tables and doing a single join on that product or
< using subselects to create bitmaps of each dimmension table match
< and merge the bitmaps to perform the join on the fact table. Some
< of these algorithms might be patented.
|
|
< * Flush cached query plans when the dependent objects change or
< when the cardinality of parameters changes dramatically
> * Flush cached query plans when the dependent objects change,
> when the cardinality of parameters changes dramatically, or
> when new ANALYZE statistics are available
|
|
Drake:
< and merge the bitmaps to perform the join on the fact table.
> and merge the bitmaps to perform the join on the fact table. Some
> of these algorithms might be patented.
|
|
* Allow star join optimizations
While our bitmap scan allows multiple indexes to be joined to get
to heap rows, a star joins allows multiple dimension _tables_ to
be joined to index into a larger main fact table. The join is
usually performed by either creating a cartesian product of all
the dimmension tables and doing a single join on that product or
using subselects to create bitmaps of each dimmension table match
and merge the bitmaps to perform the join on the fact table.
|
|
< * %Add pg_get_acldef(), pg_get_typedefault(), and pg_get_attrdef()
> * %Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
> pg_get_tabledef(), pg_get_domaindef(), pg_get_functiondef()
|
|
< * Flush cached query plans when the dependent objects change
> * Flush cached query plans when the dependent objects change or
> when the cardinality of parameters changes dramatically
|
|
J.Kuwamura
|
|
J.Kuwamura
|
|
> * Allow the count returned by SELECT, etc to be to represent as an int64
> to allow a higher range of values
|
|
|
