- 11 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
> * -Allow INET + INT8 to increment the host part of the address or
-
- 10 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
< o Allow multi-line column values to align in the proper columns > o -Allow multi-line column values to align in the proper columns
-
- 07 2月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
< * %Disallow changing default expression of a SERIAL column? > * %Disallow changing default expression of a SERIAL column
-
由 Bruce Momjian 提交于
< * Allow control over which tables are WAL-logged [walcontrol] > * Allow WAL logging to be turned off for a table, but the table > might be dropped or truncated during crash recovery [walcontrol] < 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. 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 ]. Tables using non-default logging should not use < referential integrity with default-logging tables, and tables using < stable logging probably can not have indexes. One complexity is < the handling of indexes on TOAST tables. > commit. This should be implemented using ALTER TABLE, e.g. ALTER > TABLE PERSISTENCE [ DROP | TRUNCATE | DEFAULT ]. Tables using > non-default logging should not use referential integrity with > default-logging tables. A table without dirty buffers during a > crash could perhaps avoid the drop/truncate. > > * Allow WAL logging to be turned off for a table, but the table would > avoid being truncated/dropped [walcontrol] > > To do this, only a single writer can modify the table, and writes > must happen only on new pages so the new pages can be removed during > crash recovery. Readers can continue accessing the table. Such > tables probably cannot have indexes. One complexity is the handling > of indexes on TOAST tables.
-
- 04 2月, 2006 2 次提交
-
-
由 Peter Eisentraut 提交于
modified and the server config files are reloaded
-
由 Bruce Momjian 提交于
< * Allow control over which tables are WAL-logged > * Allow control over which tables are WAL-logged [walcontrol] 1038c1038,1039 < stable logging probably can not have indexes. [walcontrol] > stable logging probably can not have indexes. One complexity is > the handling of indexes on TOAST tables.
-
- 02 2月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
> * Allow statistics collector information to be pulled from the collector > process directly, rather than requiring the collector to write a > filesystem file twice a second?
-
- 01 2月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
> * Add SQL99 WITH clause to SELECT > * Add SQL99 WITH RECURSIVE to SELECT < * Add SQL99 WITH clause to SELECT < * Add SQL99 WITH RECURSIVE to SELECT
-
由 Bruce Momjian 提交于
> > o Prevent tab completion of SET TRANSACTION from querying the > database and therefore preventing the transaction isolation > level from being set. > > Currently, SET <tab> causes a database lookup to check all > supported session variables. This query causes problems > because setting the transaction isolation level must be the > first statement of a transaction.
-
- 26 1月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
< * %Prevent INET cast to CIDR if the unmasked bits are not zero, or < zero the bits < * %Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr > * -Zero umasked bits in conversion from INET cast to CIDR > * -Prevent INET cast to CIDR from dropping netmask, SELECT '1.1.1.1'::inet::cidr
-
- 23 1月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
< o Allow an alias to be provided for the target table in < UPDATE/DELETE < < This is not SQL-spec but many DBMSs allow it. < > o -Allow an alias to be provided for the target table in > UPDATE/DELETE (Neil)
-
- 18 1月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
> o -Allow pooled connections to list all open WITH HOLD cursors
-
- 12 1月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
> * -Add sleep() function, remove from regress.c
-
- 10 1月, 2006 1 次提交
-
-
由 Bruce Momjian 提交于
< * %Allow pooled connections to list all prepared statements > * -%Allow pooled connections to list all prepared statements
-
- 06 1月, 2006 5 次提交
-
-
由 Bruce Momjian 提交于
> > * Allow SERIAL sequences to inherit permissions from the base table?
-
由 Bruce Momjian 提交于
< stable logging probably can not have indexes. [wallog] > stable logging probably can not have indexes. [walcontrol]
-
由 Bruce Momjian 提交于
< 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]
-
由 Bruce Momjian 提交于
< 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]
-
由 Bruce Momjian 提交于
> > * 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]
-
- 05 1月, 2006 2 次提交
-
-
由 Bruce Momjian 提交于
< * %Remove behavior of postmaster -o after making postmaster/postgres < flags unique > * %Remove behavior of postmaster -o
-
由 Bruce Momjian 提交于
> * -Remove BeOS and QNX-specific code
-
- 30 12月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
> * Make CLUSTER preserve recently-dead tuples per MVCC requirements
-
由 Bruce Momjian 提交于
< * Add missing rtree optimizer selectivity > * Improve selectivity functions for geometric operators
-
- 28 12月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
< * Add missing optimizer selectivities for date, r-tree, etc > * Add missing rtree optimizer selectivity
-
由 Bruce Momjian 提交于
< * %Make row-wise comparisons work per SQL spec > * -Make row-wise comparisons work per SQL spec
-
- 26 12月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
* %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)'.
-
- 23 12月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
> > A more complex solution would be to save multiple plans for different > cardinality and use the appropriate plan based on the EXECUTE values. >
-
- 18 12月, 2005 4 次提交
-
-
由 Bruce Momjian 提交于
< * 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.
-
由 Bruce Momjian 提交于
< * 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
-
由 Bruce Momjian 提交于
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.
-
由 Bruce Momjian 提交于
* 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.
-
- 17 12月, 2005 5 次提交
-
-
由 Bruce Momjian 提交于
< * %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()
-
由 Bruce Momjian 提交于
< * 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
-
由 Bruce Momjian 提交于
> * Allow the count returned by SELECT, etc to be to represent as an int64 > to allow a higher range of values
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
-
- 12 12月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
< * %Allow pooled connections to list all prepared queries > * %Allow pooled connections to list all prepared statements 28c28 < the queries prepared in the current session. > the statements prepared in the current session. 143c143 < o Allow a warm standby system to also allow read-only queries > o Allow a warm standby system to also allow read-only statements 404c404 < * Add GUC to issue notice about queries that use unjoined tables > * Add GUC to issue notice about statements that use unjoined tables 490c490 < Another idea would be to allow actual SELECT queries in a COPY. > Another idea would be to allow actual SELECT statements in a COPY. 554c554 < o Allow function argument names to be queries from PL/PgSQL > o Allow function argument names to be statements from PL/PgSQL 591c591 < o Improve psql's handling of multi-line queries > o Improve psql's handling of multi-line statements < Currently, while \e saves a single query as one entry, interactive < queries are saved one line at a time. Ideally all queries > Currently, while \e saves a single statement as one entry, interactive > statements are saved one line at a time. Ideally all statements 665c665 < o Allow query results to be automatically batched to the client > o Allow statement results to be automatically batched to the client 667c667 < Currently, all query results are transfered to the libpq > Currently, all statement results are transfered to the libpq 672c672 < One complexity is that a query like SELECT 1/col could error > One complexity is that a statement like SELECT 1/col could error 739c739 < * Allow queries across databases or servers with transaction > * Allow statements across databases or servers with transaction < inheritance, allow it to work for UPDATE and DELETE queries, and allow < it to be used for all queries with little performance impact > inheritance, allow it to work for UPDATE and DELETE statements, and allow > it to be used for all statements with little performance impact 876c876 < * Consider automatic caching of queries at various levels: > * Consider automatic caching of statements at various levels: 947c947 < a single session using multiple threads to execute a query faster. > a single session using multiple threads to execute a statement faster. 1025c1025 < * Log queries where the optimizer row estimates were dramatically > * Log statements where the optimizer row estimates were dramatically 1146c1146 < of result sets using new query protocol > of result sets using new statement protocol
-
- 11 12月, 2005 1 次提交
-
-
由 Bruce Momjian 提交于
< * Add GUC variable to run a command on database panic or < smart/fast/immediate shutdown
-
- 10 12月, 2005 2 次提交
-
-
由 Bruce Momjian 提交于
< * Allow installing to directories containing spaces > * -Allow installing to directories containing spaces
-
由 Bruce Momjian 提交于
* -Have initdb set the input DateStyle (MDY or DMY) based on locale
-