Thumbs up on this from a lurker.
I recall a previous post about some sort of progress bar hack that
would show you where in a plan a currently executing query was at. Has
any work been done on this?
Josh Reich
Jim C. Nasby wrote:
On Mon, Dec 11, 2006 at 12:24:12AM +0100, Peter Eisentraut
Ron Mayer wrote:
Gregory Stark wrote:
Ron Mayer [EMAIL PROTECTED] writes:
...vastly overestimate the number of pages .. because postgresql's guess
at the correlation being practically 0 despite the fact that the distinct
values for any given column are closely packed on a few pages.
(Not sure how we'd implement that, seeing that ANALYZE currently works
on one table at a time, but it's probably doable --- and it'd fix the
fundamental problem for correlation statistics, which is how not to try
to collect stats about an exponential number of combinations ...)
An exponential
to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
--
Joshua Reich
Finance and Corporate Development
ROOT Exchange, A Division of ROOT Markets
601 W. 26th St. / Suite 1500
New York, NY 10001
Office - (212) 645 6320 x 7101
Cell - (646) 427 7959
:
Joshua Reich [EMAIL PROTECTED] writes:
The problem is that there are new functions in cube.sql, so the output
is now different and breaks the diff (to state the obvious).
Actually, the new theory on this is that you should explicitly create
a shell type first:
CREATE TYPE cube
excessive? Can we possibly simplify things a bit?
cheers
andrew
--
Joshua Reich
Finance and Corporate Development
ROOT Exchange, A Division of ROOT Markets
601 W. 26th St. / Suite 1500
New York, NY 10001
W - (212) 645 6320 x 7101
M / T - (646) 427 7959
E - [EMAIL PROTECTED
message can get through to the mailing list cleanly
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faq
--
Joshua Reich
Finance and Corporate Development
ROOT Exchange
Can you point to me where I can get a regression diff for a failed
build. For the install-checks that I looked at on the buildfarm, I see:
== running regression test queries==
test cube ... ok
Josh
Tom Lane wrote:
[EMAIL PROTECTED] (Bruce
wrote:
Joshua Reich [EMAIL PROTECTED] writes:
Can you point to me where I can get a regression diff for a failed
build.
It's all on the webpage, just scroll down ...
regards, tom lane
---(end of broadcast)---
TIP 4
Stating the obvious, again - attached is my patch for earthdistance.
Apologies for breaking the build.
Josh
Joshua Reich wrote:
Ok. If I understand this correctly, earthdistance required cube. So,
I'll fix the test for earthdistance to work with the new cube code.
The problem
Is it safe to use the output of EXPLAIN in regression tests? I want to
make sure that certain GiST indexes are being used by sample queries,
but I am not sure if it is safe to rely on the format of EXPLAIN to be
unchanging.
Thoughts?
Josh Reich
---(end of
Just a general question - I submitted a patch for contrib/cube (adding a
new function converting everything from V0 to V1), what is the process
from here onwards? Do we have an active maintainer of this code? How is
it reviewed?
I would like to continue working on the cube stuff, as our
Tom Lane wrote:
Joshua Reich [EMAIL PROTECTED] writes:
Do we have an active maintainer of this code?
It sounds like you've just acquired that position ;-)
More than happy to take the role.
How is it reviewed?
Same as everything else, pretty much: patches go to pgsql-patches
queries==
test cube ... FAILED
==
1 of 1 tests failed.
==
I have tried this both on OS X and Linux and get similar results.
Josh Reich
Neil Conway wrote:
On Mon, 2006-07-17 at 17:55 -0400, Joshua Reich wrote:
Ok. So
I upgraded to the latest version (2.3) as per the warning after running
configure.
Josh
Andrew Dunstan wrote:
What version of bison do you have?
cheers
andrew
Joshua Reich wrote:
I have completed upgrading the cube codebase to use the V1 call
protocol. However, before I submit a patch
I just downgraded from 2.3 to 1.875 and rebuilt everything, and now it
works fine.
As per Andrew's previous email, in 2.3 the error messages were changed
from parse error to syntax error, causing the diff to fail.
Josh
Tom Lane wrote:
Joshua Reich [EMAIL PROTECTED] writes:
Andrew Dunstan
for the UR
coordinate, one for LL.
I hope people find this useful, and if so, we can add it to contrib/cube.
Source is attached.
Thanks,
Joshua Reich
(jdigittl on #postgresql)
#include postgres.h
#include utils/array.h
#include cubedata.h /* contrib/cube
Tom: Thanks for the out-of-band posting to the documentation. I think
the new version (attached) addresses your issues.
What is the general process for submitting patches? Is there a URL
someone can point me towards to learn more?
Thanks,
Josh Reich
Tom Lane wrote:
Joshua Reich [EMAIL
18 matches
Mail list logo
