| Age | Commit message (Collapse) | Author |
|---|
|
|
|
actually takes three. Please apply the following patch.
Massimo
|
|
These were bogus selectivity-estimator links, like a '>' operator
pointing to intltsel when it should use intgtsel.
|
|
making prosrc instead of proname be the link to the actual internal function.
|
|
hashjoin's hashFunc() so that it does the right thing with pass-by-value
data types (the old code would always return 0 for int2 or char values,
which would work but would slow things down a lot). Extend opr_sanity
regress test to catch more kinds of errors.
|
|
hashjoins. Extend opr_sanity regress test to help detect similar mistakes.
|
|
of 2 to save a few cycles in md.c. So, make it 2^30 not 10^9.
|
|
configuration constant to config.h.
|
|
polygon rtree, circle rtree indexes.
|
|
would sometimes generate a plan that omitted a sort step before merge.
|
|
it with configure-script tests to see whether const, inline, volatile, etc
work or not. (Curiously, configure was already doing the work to see if
const and inline were OK, but the results were not getting plugged into
config.h :-(.)
|
|
complaints (and some of my own).
|
|
|
|
function is found in prosrc field of pg_proc, not proname. This allows
multiple aliases of a built-in to all be implemented as direct builtins,
without needing a level of indirection through an SQL function. Replace
existing SQL alias functions with builtin entries accordingly.
Save a few K by not storing string names of builtin functions in fmgr's
internal table (if you really want 'em, get 'em from pg_proc...).
Update opr_sanity with a few more cross-checks.
|
|
2. Much faster btree tuples deletion in the case when first on page
index tuple is deleted (no movement to the left page(s)).
3. Remember blkno of new root page in BTPageOpaque of
left/right siblings when root page is splitted.
|
|
and newly expanded opr_sanity tests.
|
|
regress test 'type_sanity'.
|
|
It still doesn't do anything, but at least now it does nothing correctly.
|
|
|
|
|
|
Apparently, whatever these things used to link to got recycled into
something else ... but the dependent entries didn't.
|
|
configure, instead of having a bunch of crufty platform-specific guesses.
|
|
need not be bogus.
|
|
|
|
|
|
I have solved some problems with dynamic loading on NT. It is possible
to
run succesfully both trigger and plpgsql regression tests. The patch is
in
the included file "diff".
Dan
|
|
change functionality, but makes the code more ANSI C'ish.
My AIX xlc compiler barfs on all of these. Can someone please
review and apply to current.
<<port.patch>>
Thanks
Andreas
|
|
|
|
I have changed to call pg_exec_query_dest() instead of pg_exec_query().
Thanks.
Hiroshi Inoue
|
|
but at least now it does what it's supposed to do ...
|
|
define INT64_FORMAT in all cases.
|
|
results in a bogus datetime value under AlphaLinux. (Note that
the link to submit a port-specific bug on your website is broken)
-Test Case:
----------
testdb=> create table dttest (dt datetime);
testdb=> insert into dttest values ('now');
--------------------------------------------------------------------------
Solution:
---------
The basic problem is the typedefs of AbsoluteTime and RelativeTime,
which are both 'int32'. These types appear to be used synonymously
with the 'time_t' type, which on AlphaLinux is typedef'd as a 'long
int', which is 64-bits (not 32). The solution included here fixes
the datetime type (it now passes the regression test), but does not
pass the absolute and relative time regression tests. Presumably, a
more thorough investigation of how these types are used is warranted.
The included patch is from the v6.3.2 source, but can be applied to
the v6.4.2 source. Please note that there is also a RedHat-specific
patch distributed with the PostgreSQL source package from RedHat
that was applied first.
Rich Edwards
|
|
|
|
NetBSD/macppc
LinuxPPC
FreeBSD 2.2.6-RELEASE
All of them seem happy with the regression test. Note that, however,
compiling with optimization enabled on NetBSD/macppc causes an initdb
failure (other two platforms are ok). After checking the asm code, we
are suspecting that might be a compiler(egcs) bug.
Tatsuo Ishii
|
|
I would like some feedback on what the hash function for the int8 hash
function
in the ./backend/access/hash/hashfunc.c should return.
Also, could someone (maybe Tomas Lockhart?) look-over the patch and make
sure
the system table entries are correct? I've tried to research them as
much as I
could, but some of them are still not clear to me.
Thanks,
-Ryan
|
|
so that it has some SQL operators available. It's difficult to write
automated tests of a data type that you haven't even got == for...
|
|
and pg_operator. The lone error in pg_operator was reported as a bug
by Michael Reifenberger; the multiple errors in pg_proc would only have
been noticed if one invoked the functions by name rather than using
operator syntax. I guess few people do that.
|
|
From: Horak Daniel <horak@mmp.plzen-city.cz>
|
|
use of %qd...a more generic solution then having #ifdef __<INSERT OS HERE>__
in the code...
|
|
|
|
|
|
|
|
|
|
This change brings the default size of the main shmem block back under 1MB,
which is a fairly popular value for the kernel's SHMMAX parameter.
|
|
_copyResult didn't copy subPlan structure completely. _copyAgg is still
busted, apparently because of changes from EXCEPT/INTERSECT patch
(get_agg_tlist_references is no longer sufficient to find all aggregates).
No time to look at that tonight, however.
|
|
so remove them from MergeJoin node. Hack together a partial
solution for commuted mergejoin operators --- yesterday
a mergejoin int4 = int8 would crash if the planner decided to
commute it, today it works. The planner's representation of
mergejoins really needs a rewrite though.
Also, further testing of mergejoin ops in opr_sanity regress test.
|
|
right side data types. Correct the opr_sanity regress test to check these
entries properly. NOTE that opr_sanity will now fail until you do an initdb!
|
|
right sides have different data types.
|
|
without it. Sloppy, sloppy.
|
|
Move files to deadcode.
|
