Log Message:
---
Add a citation to Seltzer and Yigit's Usenix '91 paper about hash table
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 th
> > > This commit message is rather old, I remarked on its absence earlier, but
> > > better late than never I guess ;)
> >
> > Not sure what you mean. I just committed it recently. I held off
> > until after the release as requested. What do you mean by "old?"
>
> You committed it five days a
Log Message:
---
Fix vcbuild to allow building without OpenSSL and/or zlib. Magnus
Modified Files:
--
pgsql/src/tools/msvc:
mkvcbuild.pl (r1.8 -> r1.9)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/mkvcbuild.pl.diff?r1=1.8&r2=1.9)
-
Log Message:
---
vcbuild documentation from Magnus and Dave.
Added Files:
---
pgsql/src/tools/msvc:
README (r1.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/tools/msvc/README?rev=1.1&content-type=text/x-cvsweb-markup)
---(end
Log Message:
---
Done:
< * 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 a
D'Arcy J.M. Cain wrote:
> On Sun, 7 Jan 2007 21:04:09 -0800 (PST)
> Jeremy Drake <[EMAIL PROTECTED]> wrote:
> > This commit message is rather old, I remarked on its absence earlier, but
> > better late than never I guess ;)
>
> Not sure what you mean. I just committed it recently. I held off
> u
Log Message:
---
pltcl regression test needs to actually create an opclass, not just one
operator.
Modified Files:
--
pgsql/src/pl/tcl/expected:
pltcl_setup.out (r1.5 -> r1.6)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/tcl/expected/pltcl_setu
Log Message:
---
Support ORDER BY ... NULLS FIRST/LAST, and add ASC/DESC/NULLS FIRST/NULLS LAST
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
Log Message:
---
Prevent duplicate attribute names in XMLELEMENT.
Modified Files:
--
pgsql/src/backend/parser:
parse_expr.c (r1.204 -> r1.205)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/parser/parse_expr.c.diff?r1=1.204&r2=1.205)
pgsq
Log Message:
---
Added perl Makefile.PL, more or less to automatically determine where perl is
installed.
Modified Files:
--
pghotbackup:
pg_hotbackup (r1.1 -> r1.2)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pghotbackup/pghotbackup/pg_hotbackup.diff?r1=
Log Message:
---
Initial check in for pg_hotbackup.
Added Files:
---
pghotbackup:
pg_hotbackup (r1.1)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/pghotbackup/pghotbackup/pg_hotbackup?rev=1.1&content-type=text/x-cvsweb-markup)
---(end o
Log Message:
---
Updated copyright date.
Modified Files:
--
dbi-link:
copyright.txt (r1.3 -> r1.4)
(http://cvs.pgfoundry.org/cgi-bin/cvsweb.cgi/dbi-link/dbi-link/copyright.txt.diff?r1=1.3&r2=1.4)
---(end of broadcast)---
On Sun, 7 Jan 2007 21:04:09 -0800 (PST)
Jeremy Drake <[EMAIL PROTECTED]> wrote:
> This commit message is rather old, I remarked on its absence earlier, but
> better late than never I guess ;)
Not sure what you mean. I just committed it recently. I held off
until after the release as requested.
Log Message:
---
Tweak joinlist creation to avoid generating useless one-element subproblems
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
Log Message:
---
Tweak joinlist creation to avoid generating useless one-element subproblems
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
Log Message:
---
Remove cost_hashjoin's very ancient hack to discourage (once, entirely forbid)
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 ough
Log Message:
---
Remove cost_hashjoin's very ancient hack to discourage (once, entirely forbid)
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 ough
17 matches
Mail list logo
