rdelaage
/
postgresql
mirror of https://git.postgresql.org/git/postgresql.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
24,430 Commits 36 Branches 606 Tags 423 MiB
Commit Graph

2116 Commits

Author SHA1 Message Date
Bruce Momjian 80ab3e0d34 Add URL for: 
o Allow row and record variables to be set to NULL constants,
        and allow NULL tests on such variables
 2007-02-21 01:08:58 +00:00
Bruce Momjian 4816b0f452 Add: 
>
> * Consider decreasing the amount of memory used by PrivateRefCount
>
>   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00797.php
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00752.php
>
 2007-02-20 23:39:03 +00:00
Bruce Momjian a64e85eb68 Add: 
> * Increase locking when DROPing objects so dependent objects cannot
>   get dropped while the DROP operation is happening
>
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00937.php
 2007-02-20 22:29:28 +00:00
Bruce Momjian 6e6dab8c87 Add URL for: 
o Allow UPDATE/DELETE WHERE CURRENT OF cursor
> 	  http://archives.postgresql.org/pgsql-hackers/2007-01/msg01014.php
 2007-02-20 22:23:05 +00:00
Bruce Momjian 916ecf2d5d Add: 
>
> * Add missing operators for geometric data types
>
>   Some geometric types do not have the full suite of geometric operators,
>   e.g. box @> point
>
 2007-02-20 21:22:35 +00:00
Bruce Momjian 71b0cf2f6b Remove, item not needed for Win32: 
< 	o Check .pgpass file permissions
>
 2007-02-20 15:21:42 +00:00
Bruce Momjian bfc53d7da4 Add for WIN32: 
<
> 	o Check .pgpass file permissions
 2007-02-20 14:48:47 +00:00
Bruce Momjian 265124e7e0 Add: 
> * Fix IS OF so it matches the ISO specification, and add documentation
>
>   http://archives.postgresql.org/pgsql-patches/2003-08/msg00060.php
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00060.php
 2007-02-20 14:17:24 +00:00
Bruce Momjian 2673961659 Remove item: 
< 	o ARRAY[[1,2],[3,4]])[1] should return the same values as
< 	  ARRAY[[1,2],[3,4]])[1:1];
<
 2007-02-20 03:47:03 +00:00
Bruce Momjian 4acc4aa871 Update wording: 
< * Consider allowing configuration of TOAST thresholds
> * Allow user configuration of TOAST thresholds
 2007-02-19 21:08:48 +00:00
Bruce Momjian bba9ec141f Add: 
> * Consider allowing configuration of TOAST thresholds
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00213.php
>
 2007-02-19 21:07:25 +00:00
Bruce Momjian 6042bb498c Add newlines. 2007-02-19 20:42:33 +00:00
Bruce Momjian 5855d2b593 Add: 
> * Allow UPDATEs on only non-referential integrity columns not to conflict
>   with referential integrity locks
>
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00073.php
 2007-02-19 20:41:40 +00:00
Bruce Momjian c7116a4112 Add: 
> * Allow INSERT/UPDATE ... RETURNING inside a SELECT 'FROM' clause
>
>   http://archives.postgresql.org/pgsql-general/2006-09/msg00803.php
>   http://archives.postgresql.org/pgsql-hackers/2006-10/msg00693.php
>
 2007-02-19 20:06:56 +00:00
Bruce Momjian 107062e008 Done: 
> * -Add ISO day of week format 'ID' to to_char() where Monday = 1
 2007-02-19 17:58:32 +00:00
Bruce Momjian 27d6ee04b8 Done: 
> * -Add a field 'isoyear' to extract(), based on the ISO week
 2007-02-19 17:21:24 +00:00
Bruce Momjian 68c7cb5ed5 Done: 
< 	o Add long file support for binary pg_dump output
<
< 	  While Win32 supports 64-bit files, the MinGW API does not,
< 	  meaning we have to build an fseeko replacement on top of the
< 	  Win32 API, and we have to make sure MinGW handles it.  Another
< 	  option is to wait for the MinGW project to fix it, or use the
< 	  code from the LibGW32C project as a guide.
<
< 	  http://archives.postgresql.org/pgsql-hackers/2006-12/msg00551.php
<
> 	o -Add long file support for binary pg_dump output
 2007-02-19 16:36:17 +00:00
Bruce Momjian 9f6ed2f47f Update wording: 
<   Currently, ALTER USER and ALTER DATABASE support per-user and
>   Currently ALTER USER and ALTER DATABASE support per-user and
< 	  Currently, subtracting one date from another that crosses a
> 	  Currently subtracting one date from another that crosses a
<   Currently, SQL-language functions can only refer to parameters via $1, etc
>   Currently SQL-language functions can only refer to dollar parameters,
>   e.g. $1
<   Currently, queries prepared via the libpq API are planned on first
>   Currently queries prepared via the libpq API are planned on first
< 	  Currently, SET <tab> causes a database lookup to check all
> 	  Currently SET <tab> causes a database lookup to check all
< 	  Currently, all statement results are transferred to the libpq
> 	  Currently all statement results are transferred to the libpq
 2007-02-18 01:34:35 +00:00
Bruce Momjian 0e461f275b Add: 
* Allow SQL-language functions to reference parameters by parameter name

  Currently SQL-language functions can only refer to parameters via $1, etc
 2007-02-18 01:32:55 +00:00
Bruce Momjian 37a22932f2 Add: 
> * Allow holdable cursors in SPI
 2007-02-17 02:01:02 +00:00
Bruce Momjian c6ed4ead01 Add: 
>
> 		o Allow row and record variables to be set to NULL constants,
> 		  and allow NULL tests on such variables
>
> 		  Because a row is not scalar, do not allow assignment
> 		  from NULL-valued scalars.
 2007-02-17 01:35:41 +00:00
Bruce Momjian 46bd3bff62 Add: 
> 	o Consider reducing on-disk varlena length from four to two
> 	  because a heap row cannot be more than 64k in length
 2007-02-16 22:20:02 +00:00
Bruce Momjian 01191c7177 Add: 
>
> 	o Use LC_TIME for localized weekday/month names, rather than
> 	  LC_MESSAGES
>
> 	  http://archives.postgresql.org/pgsql-hackers/2006-11/msg00390.php
 2007-02-14 21:00:17 +00:00
Bruce Momjian 33d72c7351 Add: 
> * Clean up casting in /contrib/isn
>
>   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00245.php
>
 2007-02-14 04:24:42 +00:00
Bruce Momjian 7de3375f78 Add: 
> * Improve logging of prepared statements recovered during startup
>
>   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00092.php
>
 2007-02-14 04:19:37 +00:00
Bruce Momjian d7250994e6 Add URL for: 
* Allow SQL-language functions to return results from RETURNING queries
>
>   http://archives.postgresql.org/pgsql-hackers/2006-10/msg00665.php
>
 2007-02-14 02:49:37 +00:00
Bruce Momjian 65e2f55031 Add URL for: 
>
>   http://archives.postgresql.org/pgsql-performance/2006-10/msg00222.php
>
 2007-02-14 00:47:05 +00:00
Bruce Momjian e4f45d29be Add URL for: 
* Update Bonjour to work with newer cross-platform SDK

>   http://archives.postgresql.org/pgsql-patches/2006-10/msg00048.php
 2007-02-13 23:23:11 +00:00
Bruce Momjian 6e5c64b551 Add: 
> * Improve failure message when DROP DATABASE is used on a database that
>   has prepared transactions
 2007-02-13 19:57:09 +00:00
Bruce Momjian b9c65aed82 Add URL for: 
* Update Bonjour to work with newer cross-platform SDK

>
>   http://archives.postgresql.org/pgsql-hackers/2006-09/msg02238.php
>
 2007-02-13 18:08:39 +00:00
Bruce Momjian 954eb25a11 Add: 
> * Update our code to handle 64-bit timezone files to match the zic
>   source code, which now uses them
 2007-02-13 17:03:16 +00:00
Bruce Momjian 1ad2f04bf2 Add blank line. 2007-02-09 03:39:59 +00:00
Bruce Momjian 9eddc28197 Add URL for: 
<
>   http://archives.postgresql.org/pgsql-hackers/2007-02/msg00435.php
 2007-02-09 03:39:39 +00:00
Bruce Momjian 19d561cbd0 Done! 
< * Merge xmin/xmax/cmin/cmax back into three header fields
<
<   Before subtransactions, there used to be only three fields needed to
<   store these four values. This was possible because only the current
<   transaction looks at the cmin/cmax values. If the current transaction
<   created and expired the row the fields stored where xmin (same as
<   xmax), cmin, cmax, and if the transaction was expiring a row from a
<   another transaction, the fields stored were xmin (cmin was not
<   needed), xmax, and cmax. Such a system worked because a transaction
<   could only see rows from another completed transaction. However,
<   subtransactions can see rows from outer transactions, and once the
<   subtransaction completes, the outer transaction continues, requiring
<   the storage of all four fields. With subtransactions, an outer
<   transaction can create a row, a subtransaction expire it, and when the
<   subtransaction completes, the outer transaction still has to have
<   proper visibility of the row's cmin, for example, for cursors.
<
<   One possible solution is to create a phantom cid which represents a
<   cmin/cmax pair and is stored in local memory.  Another idea is to
<   store both cmin and cmax only in local memory.
<
> * -Merge xmin/xmax/cmin/cmax back into three header fields
 2007-02-09 03:37:45 +00:00
Bruce Momjian aba039df66 Update: 
< * Consider placing all sequences in a single table
> * Consider placing all sequences in a single table, or create a system
>   view
 2007-02-09 01:29:48 +00:00
Bruce Momjian 5bdf44c647 Update: 
< * Consider placing all sequences in a single table, now that system
<   tables are full transactional
> * Consider placing all sequences in a single table
 2007-02-09 00:34:31 +00:00
Bruce Momjian 18d36f9e19 Add: 
> * Consider placing all sequences in a single table, now that system
>   tables are full transactional
 2007-02-09 00:32:15 +00:00
Bruce Momjian 2737f304ca Add URL for: 
* Add support for SQL-standard GENERATED/IDENTITY columns
>   http://archives.postgresql.org/pgsql-hackers/2006-08/msg00038.php
 2007-02-08 21:51:50 +00:00
Bruce Momjian 869585cc8f Split apart entries, one done now: 
* -Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h
* Consider making NAMEDATALEN more configurable in future releases
 2007-02-06 16:44:14 +00:00
Bruce Momjian fdd4a1ff0d Updated TODO item: 
> 	o Add a \set variable to control whether \s displays line numbers

> 	  Another option is to add \# which lists line numbers, and
> 	  allows command execution.
> 	  http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
 2007-02-05 17:17:13 +00:00
Bruce Momjian fcbddea8b7 Modify: 
< 	o Add \# to list command history like \s, but with line numbers
> 	o Add \# to list and execute command history
 2007-02-05 16:49:13 +00:00
Bruce Momjian 03d442ca60 Add: 
>
> * Allow custom variable classes that can restrict who can set the values
>
>   http://archives.postgresql.org/pgsql-hackers/2006-11/msg00911.php
>
 2007-02-04 04:06:08 +00:00
Bruce Momjian 1d6653ee80 Update URL for: 
* Allow sequential scans to take advantage of other concurrent
  sequential scans, also called "Synchronised Scanning"
 2007-02-04 02:32:03 +00:00
Bruce Momjian 28019984e9 Add: 
>
> 	o Add \# to list command history like \s, but with line numbers
>
> 	  http://archives.postgresql.org/pgsql-hackers/2006-12/msg00255.php
>
 2007-02-04 01:50:59 +00:00
Bruce Momjian 300c43e303 Add URLs for: 
* Allow sequential scans to take advantage of other concurrent
  sequential scans, also called "Synchronised Scanning"
>   http://archives.postgresql.org/pgsql-patches/2006-12/msg00076.php
>   http://archives.postgresql.org/pgsql-hackers/2006-12/msg00408.php
 2007-02-03 23:52:19 +00:00
Bruce Momjian b6f6284802 Add: 
> 	  o Allow recovery.conf to allow the same syntax as
> 	    postgresql.conf, including quoting
>
> 	    http://archives.postgresql.org/pgsql-hackers/2006-12/msg00497.php
 2007-02-03 22:32:49 +00:00
Bruce Momjian b1b9c364cc Add patches thread for: 
* Reduce checkpoint performance degredation by forcing data to disk
  more evenly

>   http://archives.postgresql.org/pgsql-patches/2006-12/msg00104.php
 2007-02-03 01:59:27 +00:00
Bruce Momjian 635425d845 Add URL for: 
* Allow sequential scans to take advantage of other concurrent
  sequential scans, also called "Synchronised Scanning"
>
>   http://archives.postgresql.org/pgsql-hackers/2006-12/msg00784.php
 2007-02-02 23:05:36 +00:00
Bruce Momjian 69b90c49bc Add: 
> * Reduce checkpoint performance degredation by forcing data to disk
>   more evenly
>
>   http://archives.postgresql.org/pgsql-hackers/2006-12/msg00337.php
>   http://archives.postgresql.org/pgsql-hackers/2007-01/msg00079.php
 2007-02-02 22:55:08 +00:00
Bruce Momjian 99be3fa3ee Add URL for: 
o Fix RENAME to work on variables other than OLD/NEW
> 		  http://archives.postgresql.org/pgsql-hackers/2007-01/msg01587.php
 2007-02-02 21:34:39 +00:00