- 19 Sep, 2006 1 commit
-
-
Bruce Momjian authored
< * -Make postmater and postgres options distinct so the postmaster -o < option is no longer needed < * -Allow pooled connections to list all prepared statements < < This would allow an application inheriting a pooled connection to know < the statements prepared in the current session. < < * -Re-enable the GUC full_page_writes in 8.2 when reliability issues have < been addressed < o -Add "include file" functionality in postgresql.conf < o -Allow per-database permissions to be set via GRANT < < Allow database connection checks based on GRANT rules in < addition to the existing access checks in pg_hba.conf. < < o -Issue a warning if a change-on-restart-only postgresql.conf value > o Issue a warning if a change-on-restart-only postgresql.conf value < o -Automatically force archiving of partially-filled WAL files when < pg_stop_backup() is called or the server is stopped < o -Add reporting of the current WAL file and offset, perhaps as < part of partial log file archiving < * -Allow server logs to be remotely read and removed using SQL commands < * -Allow protocol-level BIND parameter values to be logged < * -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 < * -Allow INET + INT8 to increment the host part of the address or < throw an error on overflow < * -Add 'tid != tid ' operator for use in corruption recovery < o -Allow customization of the known set of TZ names (generalize the < present australian_timezones hack) < o -Allow timezone names in SQL strings, '2006-05-24 21:11 < Americas/New_York'::timestamptz < o -Add support for day-time syntax, INTERVAL '1 2:03:04' DAY TO < SECOND < o -Allow NULLs in arrays < * -Add transaction_timestamp(), statement_timestamp(), clock_timestamp() < functionality < < Current CURRENT_TIMESTAMP returns the start time of the current < transaction, and gettimeofday() returns the wallclock time. This will < make time reporting more consistent and will allow reporting of < the statement start time. < < * -Allow to_char() to print localized month names < * -Add sleep() function, remove from regress.c < * -Allow user-defined functions retuning a domain value to enforce domain < constraints < * -Allow TRUNCATE ... CASCADE/RESTRICT < < This is like DELETE CASCADE, but truncates. < < * -Add COMMENT ON for all cluster global objects (roles, databases < and tablespaces) < * -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)'. < < * -Enable escape_string_warning and standard_conforming_strings > * Enable standard_conforming_strings < o -Add ON COMMIT capability to CREATE TABLE AS ... SELECT < o -Allow an alias to be provided for the target table in < UPDATE/DELETE (Neil) < o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating < multiple columns < o -Add ALTER TABLE tab INHERIT / NO INHERIT parent < o -Have COPY return the number of rows loaded/unloaded? < o -Allow COPY (SELECT ...) TO 'filename' < < o -Allow pooled connections to list all open WITH HOLD cursors < < Because WITH HOLD cursors exist outside transactions, this allows < them to be listed so they can be closed. < < o -Allow INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..) < o -Allow INSERT/UPDATE ... RETURNING new.col or old.col < o -Allow PL/python to return composite types and result sets < < * -Have initdb set the input DateStyle (MDY or DMY) based on locale < o -Improve psql's handling of multi-line statements < < Currently, while \e saves a single statement as one entry, interactive < statements are saved one line at a time. Ideally all statements < would be saved like \e does. < < o -Allow multi-line column values to align in the proper columns < < If the second output column value is 'a\nb', the 'b' should appear < in the second display column, rather than the first column as it < does now. < < o -Display IN, INOUT, and OUT parameters in \df < o -Allow pg_dump to use multiple -t and -n switches, exclusion < ability, and regular expression object matching < o -Update pg_dump and psql to use the new COPY libpq API (Christopher) < o -Add a function to support Parse/DescribeStatement capability < * -Add fillfactor to control reserved free space during index creation < * -Add system view to show free space map contents < * -Allow installing to directories containing spaces < < This is possible if proper quoting is added to the makefiles for the < install targets. Because PostgreSQL supports relocatable installs, it < is already possible to install into a directory that doesn't contain < spaces and then copy the install to a directory with spaces. < < * -%Clean up compiler warnings (especially with gcc version 4) < * -Remove BeOS and QNX-specific code < o -Port contrib/xml2
-
- 18 Sep, 2006 4 commits
-
-
-
-
Bruce Momjian authored
> > * Set client encoding based on the client operating system encoding > > Currently client_encoding is set in postgresql.conf, which > defaults to the server encoding.
-
-
- 16 Sep, 2006 1 commit
-
-
Bruce Momjian authored
< o Reorder physical storage order to reduce padding? < < This involves having the user-specified order of columns < be different from the physical order. SELECT * would < need to reorder the physical values to match the < user-specified ordering. < < o Store disk pages with no alignment/padding? < < This necessitates adding CPU-required padding when moving < rows from disk to memory. < < One idea is to store the header in network byte order (high bits < first), and read the high bits to determine the header length. < http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php > One idea is to create zero-or-one-byte-header versions > of varlena data types. In involves setting the high-bit and > 0-127 length in the single-byte header, or clear the high bit > and store the 7-bit ASCII value in the rest of the byte. > The small-header versions have no alignment requirements. > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01372.php
-
- 14 Sep, 2006 9 commits
-
-
Bruce Momjian authored
< * -Allow PREPARE to automatically determine parameter types based on the SQL < statement (Neil)
-
Bruce Momjian authored
< * -Allow protocol-level BIND parameter values to be logged, if text mode > * -Allow protocol-level BIND parameter values to be logged
-
Bruce Momjian authored
< o -Allow commenting of variables in postgresql.conf to restore them > o Allow commenting of variables in postgresql.conf to restore them
-
Bruce Momjian authored
< * Research storing only active XIDs in subtransaction cache
-
Bruce Momjian authored
> * Research storing only active XIDs in subtransaction cache
-
Bruce Momjian authored
> > * Improve XML support > > http://developer.postgresql.org/index.php/XML_Support
-
Bruce Momjian authored
> One idea is to store the header in network byte order (high bits > first), and read the high bits to determine the header length.
-
-
Bruce Momjian authored
< o Store disk pages with no alignment/padding? > > This involves having the user-specified order of columns > be different from the physical order. SELECT * would > need to reorder the physical values to match the > user-specified ordering. > > o Store disk pages with no alignment/padding? > > This necessitates adding CPU-required padding when moving > rows from disk to memory. > > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg00848.php >
-
- 12 Sep, 2006 1 commit
-
-
Bruce Momjian authored
> * David is David Fetter <david@fetter.org>
-
- 10 Sep, 2006 1 commit
-
-
Bruce Momjian authored
< * Research storing disk pages with no alignment/padding > * Consider ways of storing rows more compactly on disk > > o Store disk pages with no alignment/padding? > o Reorder physical storage order to reduce padding? > o Support a smaller header for short variable-length fields? > o Reduce the row header size?
-
- 03 Sep, 2006 2 commits
-
-
Bruce Momjian authored
< * Change LIMIT/OFFSET and FETCH/MOVE to use int8
-
Bruce Momjian authored
< * -Change LIMIT/OFFSET and FETCH/MOVE to use int8 > * Change LIMIT/OFFSET and FETCH/MOVE to use int8
-
- 02 Sep, 2006 5 commits
-
-
Bruce Momjian authored
> * Simplify ability to create partitioned tables > > This would allow creation of partitioned tables without requiring > creation of rules for INSERT/UPDATE/DELETE, and constraints for > rapid partition selection. Options could include range and hash > partition selection. > > * Allow auto-selection of partitioned tables for min/max() operations
-
-
Bruce Momjian authored
< Last updated: Sat Sep 2 08:31:04 EDT 2006 > Last updated: Sat Sep 2 16:31:46 EDT 2006 < o Allow UPDATE tab SET ROW (col, ...) = (...) for updating multiple < columns > o -Allow UPDATE tab SET ROW (col, ...) = (val, ...) for updating > multiple columns > o Allow UPDATE tab SET ROW (col, ...) = (SELECT...) < A subselect can also be used as the value source.
-
Bruce Momjian authored
< o -Allow PL/python to composite types and result sets > o -Allow PL/python to return composite types and result sets
-
Bruce Momjian authored
o -Allow PL/python to composite types and result sets
-
- 31 Aug, 2006 1 commit
-
-
Bruce Momjian authored
< Last updated: Tue Aug 29 12:21:52 EDT 2006 > Last updated: Wed Aug 30 20:34:28 EDT 2006 < o Allow COPY (SELECT ...) TO 'filename' < < COPY should also be able to output views using COPY (SELECT < * FROM view) TO 'filename' internally. < http://archives.postgresql.org/pgsql-patches/2005-09/msg00148.php > o -Allow COPY (SELECT ...) TO 'filename'
-
- 29 Aug, 2006 1 commit
-
-
Bruce Momjian authored
> o Turn on by default
-
- 28 Aug, 2006 3 commits
-
-
Bruce Momjian authored
> o Allow DEFERRABLE and end-of-statement UNIQUE constraints? > > This would allow UPDATE tab SET col = col + 1 to work if col has > a unique index. Currently, uniqueness checks are done while the > command is being executed, rather than at the end of the statement > or transaction. > < < * Allow DEFERRABLE and end-of-statement UNIQUE constraints? < < This would allow UPDATE tab SET col = col + 1 to work if col has < a unique index. Currently, uniqueness checks are done while the < command is being executed, rather than at the end of the statement < or transaction.
-
Bruce Momjian authored
< * Allow DEFERRABLE UNIQUE constraints? > * Allow DEFERRABLE and end-of-statement UNIQUE constraints? > > This would allow UPDATE tab SET col = col + 1 to work if col has > a unique index. Currently, uniqueness checks are done while the > command is being executed, rather than at the end of the statement > or transaction. >
- 25 Aug, 2006 2 commits
-
-
Bruce Momjian authored
-
Bruce Momjian authored
< > * Implement SQL:2003 window functions
-
- 24 Aug, 2006 1 commit
-
-
Bruce Momjian authored
> * Allow inlining of set-returning functions
-
- 23 Aug, 2006 2 commits
-
-
Bruce Momjian authored
< * All backends running as threads in a single process (not want) > * All backends running as threads in a single process (not wanted) < * Optimizer hints (not want) > * Optimizer hints (not wanted) > > * Allow AS in "SELECT col AS label" to be optional (not wanted) > > Because we support postfix operators, it isn't possible to make AS > optional and continue to use bison. > http://archives.postgresql.org/pgsql-sql/2006-08/msg00164.php
-
Bruce Momjian authored
< o Allow COPY to output from SELECT > o Allow COPY (SELECT ...) TO 'filename' < COPY should also be able to output views. > COPY should also be able to output views using COPY (SELECT > * FROM view) TO 'filename' internally.
-
- 22 Aug, 2006 1 commit
-
-
Bruce Momjian authored
> > These would be for application use, not for use by pg_dump. >
-
- 21 Aug, 2006 2 commits
-
-
Bruce Momjian authored
< o Add a function to support Parse/DescribeStatement capability > o -Add a function to support Parse/DescribeStatement capability
-
Bruce Momjian authored
< * %Disallow changing DEFAULT expression of a SERIAL column? < < This should be done only if the existing SERIAL problems cannot be < fixed. < < * %Disallow ALTER SEQUENCE changes for SERIAL sequences because pg_dump < does not dump the changes
-
- 17 Aug, 2006 2 commits
-
-
Bruce Momjian authored
< * Add support for arrays of domains > o Add support for arrays of domains > o Add support for arrays of complex types
-
Bruce Momjian authored
> * Support a data type with specific enumerated values (ENUM) > > http://archives.postgresql.org/pgsql-hackers/2006-08/msg00979.php
-
- 16 Aug, 2006 1 commit
-
-
Bruce Momjian authored
> * Add support for arrays of domains
-