- 18 1月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
declarations are ignored and removed, in binary mode they are honored as specified by the XML standard.
-
- 17 1月, 2007 4 次提交
-
-
由 Bruce Momjian 提交于
-
由 Neil Conway 提交于
The implementation is somewhat ugly logic-wise, but I don't see an easy way to make it more concise. When writing this, I noticed that my previous implementation of width_bucket() doesn't handle NaN correctly: postgres=# select width_bucket('NaN', 1, 5, 5); width_bucket -------------- 6 (1 row) AFAICS SQL:2003 does not define a NaN value, so it doesn't address how width_bucket() should behave here. The patch changes width_bucket() so that ereport(ERROR) is raised if NaN is specified for the operand or the lower or upper bounds to width_bucket(). For float8, NaN is disallowed for any of the floating-point inputs, and +/- infinity is disallowed for the histogram bounds (but allowed for the operand). Update docs and regression tests, bump the catversion.
-
由 Neil Conway 提交于
existing TODO items, and re-add a TODO item for an "estimated count" capability.
-
由 Alvaro Herrera 提交于
-
- 16 1月, 2007 1 次提交
-
-
由 Neil Conway 提交于
roles and tablespaces, no longer users and groups. Per Dave Page. Backport to 8.2 and 8.1.
-
- 15 1月, 2007 1 次提交
-
-
由 Neil Conway 提交于
Per recent -hackers thread, this is noteworthy because Postgres behaves differently from most implementations of NaN, including IEEE754.
-
- 13 1月, 2007 3 次提交
-
-
由 Bruce Momjian 提交于
< o Fix memory leak from exceptions < < http://archives.postgresql.org/pgsql-performance/2006-06/msg00305.php < < * Allow constraint_exclusion to work for UNIONs like it does for < inheritance, allow it to work for UPDATE and DELETE statements, and allow < it to be used for all statements with little performance impact < < * Add estimated_count(*) to return an estimate of COUNT(*) < < This would use the planner ANALYZE statistics to return an estimated < count. < http://archives.postgresql.org/pgsql-hackers/2005-11/msg00943.php
-
由 Tom Lane 提交于
standard convention the 21st century runs from 2001-2100, not 2000-2099, so make it work like that. Per bug #2885 from Akio Iwaasa. Backpatch to 8.2, but no further, since this is really a definitional change; users of older branches are probably more interested in stability.
-
由 Bruce Momjian 提交于
-
- 11 1月, 2007 8 次提交
-
-
由 Bruce Momjian 提交于
> o Fix transaction restriction checks for CREATE DATABASE and > other commands > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00133.php
-
由 Bruce Momjian 提交于
> o Extend timezone code to allow 64-bit values so we can > represent years beyond 2038 > > http://archives.postgresql.org/pgsql-hackers/2006-09/msg01363.php >
-
由 Bruce Momjian 提交于
> * Move NAMEDATALEN from postgres_ext.h to pg_config_manual.h and > consider making it more configurable in future releases
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
Documentation/comment improvements.
-
由 Bruce Momjian 提交于
- 10 1月, 2007 8 次提交
-
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> > * Improve merge join performance by allowing mark/restore of > tuple sources > > http://archives.postgresql.org/pgsql-hackers/2007-01/msg00096.php >
-
由 Bruce Momjian 提交于
which was obsoleted by RFC 3629. Michael Fuhr
-
由 Bruce Momjian 提交于
indexes; add 'draft' option to disable it.
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
> * -Add ability to monitor the use of temporary sort files
-
由 Bruce Momjian 提交于
Bill Moran
-
由 Tom Lane 提交于
out the common error that ORDER BY x, y DESC does not mean the same as ORDER BY x DESC, y DESC.
-
- 09 1月, 2007 2 次提交
-
-
由 Bruce Momjian 提交于
< * Allow the creation of indexes with mixed ascending/descending > * -Allow the creation of indexes with mixed ascending/descending < < This is possible now by creating an operator class with reversed sort < operators. One complexity is that NULLs would then appear at the start < of the result set, and this might affect certain sort types, like < merge join. <
-
由 Tom Lane 提交于
per-column options for btree indexes. The planner's support for this is still pretty rudimentary; it does not yet know how to plan mergejoins with nondefault ordering options. The documentation is pretty rudimentary, too. I'll work on improving that stuff later. Note incompatible change from prior behavior: ORDER BY ... USING will now be rejected if the operator is not a less-than or greater-than member of some btree opclass. This prevents less-than-sane behavior if an operator that doesn't actually define a proper sort ordering is selected.
-
- 08 1月, 2007 1 次提交
-
-
由 Peter Eisentraut 提交于
-
- 07 1月, 2007 10 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Bruce Momjian 提交于
< * %Allow the identifier length to be increased via a configure option
-
由 Bruce Momjian 提交于
< * Improve the MONEY data type > * -Make 64-bit version of the MONEY data type > * Add locale-aware MONEY type, and support multiple currencies < Change the MONEY data type to use DECIMAL internally, with special < locale-aware output formatting. < http://archives.postgresql.org/pgsql-hackers/2006-09/msg01107.php
-
由 Bruce Momjian 提交于
> * -Allow user-defined types to accept 'typmod' parameters
-
由 Bruce Momjian 提交于
> > * 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.
-
由 Bruce Momjian 提交于
> 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
-
由 Bruce Momjian 提交于
< * Allow CREATE INDEX to take an additional parameter for use with < special index types
-
由 Bruce Momjian 提交于
< * 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 > > >
-
由 Bruce Momjian 提交于
> * -Allow the pg_xlog directory location to be specified during initdb
-
由 Bruce Momjian 提交于
Euler Taveira de Oliveira
-
- 06 1月, 2007 1 次提交
-
-
由 Bruce Momjian 提交于
-