| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
FAMILY; and add FAMILY option to CREATE OPERATOR CLASS to allow adding a
class to a pre-existing family. Per previous discussion. Man, what a
tedious lot of cutting and pasting ...
|
| |
|
|
|
|
|
| |
values. Point to /include/ntstatus.h for an exception list, rather than
a URL.
|
|
|
|
| |
than hex codes, using FormatMessage().
|
| |
|
|
|
|
|
|
|
|
|
|
| |
which I had removed in the first cut of the EquivalenceClass rewrite to
simplify that patch a little. But it's still important --- in a four-way
join problem mergejoinscansel() was eating about 40% of the planning time
according to gprof. Also, improve the EquivalenceClass code to re-use
join RestrictInfos rather than generating fresh ones for each join
considered. This saves some memory space but more importantly improves
the effectiveness of caching planning info in RestrictInfos.
|
| |
|
| |
|
|
|
|
| |
exception value in hex, and give a URL where the value can be looked-up.
|
| |
|
|
|
|
|
| |
tuples, which is entirely possible with custom scripts (consider
RETURNING, EXPLAIN, etc).
|
|
|
|
|
|
|
|
|
|
|
|
| |
columns procost and prorows, to allow simple user adjustment of the estimated
cost of a function call, as well as control of the estimated number of rows
returned by a set-returning function. We might eventually wish to extend this
to allow function-specific estimation routines, but there seems to be
consensus that we should try a simple constant estimate first. In particular
this provides a relatively simple way to control the order in which different
WHERE clauses are applied in a plan node, which is a Good Thing in view of the
fact that the recent EquivalenceClass planner rewrite made that much less
predictable than before.
|
| |
|
|
|
|
| |
mentioned before the system directories.
|
|
|
|
| |
a couple of syscache lookups in make_pathkey_from_sortinfo().
|
|
|
|
|
| |
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg01107.php
|
|
|
|
|
|
|
| |
provide just a boolean 'amcanorder', instead of fields that specify the
sort operator strategy numbers. We have decided to require ordering-capable
AMs to use btree-compatible strategy numbers, so the old fields are
overkill (and indeed misleading about what's allowed).
|
|
|
|
|
|
| |
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg01188.php
> http://archives.postgresql.org/pgsql-hackers/2007-01/msg00121.php
|
| |
|
|
|
|
| |
pgsql-patches discussion of September 20, 2006. Bump the catversion.
|
|
|
|
| |
Backpatch to 8.2.X for new initdbs.
|
| |
|
|
|
|
|
|
|
|
| |
match the postgresql.conf file. Also add units to descriptions that
lacked them. Wording improvements. Mention pg_settings.unit as the way
to find the default units for setting.
Backpatch to 8.2.X.
|
| |
|
|
|
|
|
| |
Previously, disabled triggers were not displayed any differently than
enabled ones, which was quite misleading. Patch from Brendan Jurd.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
representation of equivalence classes of variables. This is an extensive
rewrite, but it brings a number of benefits:
* planner no longer fails in the presence of "incomplete" operator families
that don't offer operators for every possible combination of datatypes.
* avoid generating and then discarding redundant equality clauses.
* remove bogus assumption that derived equalities always use operators
named "=".
* mergejoins can work with a variety of sort orders (e.g., descending) now,
instead of tying each mergejoinable operator to exactly one sort order.
* better recognition of redundant sort columns.
* can make use of equalities appearing underneath an outer join.
|
|
|
|
|
|
|
| |
currentMarkData from IndexScanDesc to the opaque structs for the
AMs that need this information (currently gist and hash).
Patch from Heikki Linnakangas, fixes by Neil Conway.
|
| |
|
| |
|
| |
|
|
|
|
| |
rather than a value too high.
|
|
|
|
| |
HTML in HTML mode. Patch from Jeremy Drake.
|
|
|
|
| |
Backpatch to 8.2.
|
|
|
|
|
| |
might lead to a previously installed libpq being used instead. But we
don't actually have to link with libpq here at all, so remove it.
|
|
|
|
| |
other test code.
|
|
|
|
| |
function is_log_level_output(), for code clarity.
|
| |
|
|
|
|
| |
function xmlagg.
|
|
|
|
|
|
| |
< first.
> first. There is also a developer's wiki at
> http://developer.postgresql.org.
|
|
|
|
| |
for its header comment.
|
|
|
|
|
|
|
|
|
|
|
| |
> o Allow multiple vacuums so large tables do not starve small
> tables
>
> http://archives.postgresql.org/pgsql-general/2007-01/msg00031.php
>
> o Improve control of auto-vacuum
>
> http://archives.postgresql.org/pgsql-hackers/2006-12/msg00876.php
|
|
|
|
| |
"input" and "output" dirs be necessarily present.
|
|
|
|
|
| |
* Add Globally/Universally Unique Identifier (GUID/UUID)
> http://archives.postgresql.org/pgsql-general/2007-01/msg00853.php
|
|
|
|
|
| |
with new GUC parameter "xmlbinary" that controls the output encoding, as
per SQL/XML standard.
|
|
|
|
|
|
|
| |
the generated files, to help Visual C++ to run these tests. The tests still
pass in VPATH and normal builds.
Patch from Magnus Hagander, editorialized by me.
|
| |
|
|
|
|
|
| |
declarations are ignored and removed, in binary mode they are honored as
specified by the XML standard.
|
|
|
|
|
| |
for aggregates. This is OK for current uses but could burn somebody
someday...
|
|
|
|
| |
pending fsyncs during DROP DATABASE. Obviously necessary in hindsight :-(
|
|
|
|
|
| |
dependency on the platform's floating point implementation. Per
report from Stefan Kaltenbrunner.
|