- 11 1月, 2007 1 次提交
-
-
由 Tom Lane 提交于
which comparison operators to use for plan nodes involving tuple comparison (Agg, Group, Unique, SetOp). Formerly the executor looked up the default equality operator for the datatype, which was really pretty shaky, since it's possible that the data being fed to the node is sorted according to some nondefault operator class that could have an incompatible idea of equality. The planner knows what it has sorted by and therefore can provide the right equality operator to use. Also, this change moves a couple of catalog lookups out of the executor and into the planner, which should help startup time for pre-planned queries by some small amount. Modify the planner to remove some other cavalier assumptions about always being able to use the default operators. Also add "nulls first/last" info to the Plan node for a mergejoin --- neither the executor nor the planner can cope yet, but at least the API is in place.
-
- 10 1月, 2007 14 次提交
-
-
由 Neil Conway 提交于
1) gendef works from inside visual studio - use a tempfile instead of redirection, because for some reason you can't redirect dumpbin from inside (patch from Joachim Wieland) 2) gendef must process only *.obj, or you get weird errors in some build scenarios when it tries to process a logfile Magnus Hagander
-
由 Neil Conway 提交于
the same output level that was used when building a single project before, and really needed to get reasonable information about what happens (non-verbose just says "starting build of foo" and "done building foo", more or less). Magnus Hagander
-
由 Bruce Momjian 提交于
-
由 Bruce Momjian 提交于
-
由 Tatsuo Ishii 提交于
-
由 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 提交于
research.
-
由 Bruce Momjian 提交于
nattr field, and rename the field. Heikki Linnakangas
-
由 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 9 次提交
-
-
由 Tom Lane 提交于
management. The paper clearly describes many of the ideas embodied in our current hashing code, but as far as I could find out there is not a direct code heritage. (Mike Olsen recalls discussion of this paper at Postgres meetings but believes it "informed the Postgres implementation probably just at the design level". Margo herself says she wasn't involved with Postgres' hash code.) Credit where credit is due 'n all that, even if fifteen years after the fact.
-
由 Tom Lane 提交于
-
由 Tom Lane 提交于
-
由 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 提交于
-
由 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.
-
由 Peter Eisentraut 提交于
-
由 Tom Lane 提交于
when collapsing of JOIN trees is stopped by join_collapse_limit. For instance a list of 11 LEFT JOINs with limit 8 now produces something like ((1 2 3 4 5 6 7 8) 9 10 11 12) instead of (((1 2 3 4 5 6 7 8) (9)) 10 11 12) The latter structure is really only required for a FULL JOIN. Noted while studying an example from Shane Ambler.
-
由 Tom Lane 提交于
hash joins with the estimated-larger relation on the inside. There are several cases where doing that makes perfect sense, and in cases where it doesn't, the regular cost computation really ought to be able to figure that out. Make some marginal tweaks in said computation to try to get results approximating reality a bit better. Per an example from Shane Ambler. Also, fix an oversight in the original patch to add seq_page_cost: the costs of spilling a hash join to disk should be scaled by seq_page_cost.
-
- 08 1月, 2007 2 次提交
-
-
由 Peter Eisentraut 提交于
- correct error codes - do syntax checks in correct order - strip leading spaces of argument
-
由 Peter Eisentraut 提交于
-
- 07 1月, 2007 14 次提交
-
-
由 Peter Eisentraut 提交于
-
由 Peter Eisentraut 提交于
hand-crafted parser for the XML declaration, because libxml doesn't seem to allow this.
-
由 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 提交于
-
由 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
-
由 Peter Eisentraut 提交于
sets the items, and serializes the value back (rather than adding an arbitrary number of XML preambles as before). The libxml memory management via palloc had to be disabled because it crashes when libxml tries to access memory that was helpfully freed earlier by PostgreSQL. This needs further thought.
-
由 Tom Lane 提交于
properly when doing a lookahead. The lack of this was causing various interesting misbehaviors when one tries to use "with" as a plain identifier.
-